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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully covered. The description adds the return content (environments, rollback targets), which is useful, but that overlaps with the existing output schema and adds little behavioral context. Appropriate baseline for an annotated read tool.

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?

A single efficient sentence that is front-loaded with the verb and resource, and appends the scope detail without waste.

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?

For a one-parameter read tool, the description plus rich annotations and an output schema cover most of what an agent needs. The remaining gap is the missing explanation of the apiId parameter and any usage routing against deployment siblings.

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?

Schema description coverage is 0%, so the description must carry the burden for the single 'apiId' parameter. It only implies the parameter via 'for an API', offering no format, identifier type, or constraints. Partial compensation, but the gap remains.

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?

States a specific verb and resource ('Get full deployment state') and adds scope detail ('including environments and rollback targets for an API'), so the agent knows this returns current deployment configuration rather than history. It does not explicitly distinguish itself from siblings like deployment_history or deployment_list, keeping it short of a 5.

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?

There is no when-to-use guidance and no routing to alternatives. With many sibling tools (deployment_history, deployment_list, deployment_promote, deployment_rollback), the agent gets no signal about which to pick for which situation. Usage is only implied by the phrase 'deployment state'.

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