deploy_release_get

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. States it fetches inventory (implying read-only) and lists returned data. Mentions 'Canonical SDK errors are preserved', adding error transparency. Could explicitly declare lack of side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose and return list. No extraneous words. Every sentence serves a clear function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations. Description covers purpose, return contents, a parameter usage hint, and error behavior. For a simple fetch tool, this is largely complete, though prerequisites or rate limits are not mentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 3 parameters have descriptions in the schema (100% coverage). The description adds minimal value beyond the schema: only a brief note on site_limit usage. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Describes the tool as 'Fetch a release inventory by id' — a specific verb+resource. Lists 7 return categories, clearly distinguishing from siblings like deploy_list (list releases) and deploy_release_diff (compare releases).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a parameter usage tip ('Use `site_limit` to cap large site inventories') but no explicit guidance on when to use this vs. alternative tools like deploy_release_active or deploy_list. Context could be stronger.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.