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

Annotations cover the safety profile, but the description adds substantial context they don't: 409 refusal conditions, the rule that a concurrent in-flight save is refused rather than deployed, single-operation-at-a-time locking with the running job named in the refusal, and platform-update refusals. This is exactly the extra behavioral detail the annotations can't provide.

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?

Front-loaded with purpose and scope, then structured around refusal conditions and async behavior. It is dense and slightly run-on, but nearly every clause carries operational information an agent needs; little is redundant with the schema.

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 an asynchronous mutation with no output schema, the description supplies the missing pieces: the returned job_id, polling via get_job_status, and concurrency/retry guidance. Nothing an agent needs to invoke and follow up on this call is absent.

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 coverage is 100% with a single parameter, so the schema already carries the full semantics; the description's 'relational or graph project' note duplicates the schema's own parenthetical. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Starts with a specific verb+resource+scope: 'Rebuild and roll out a project's staging environment from the schema it runs, with NO schema change.' It explicitly distinguishes itself from deploy_staging (which applies unapplied schema changes) and deploy_production (which targets production), so an agent can route correctly without opening a schema.

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?

Names the alternatives and the exact conditions that select them: deploy_staging 'deploys those' when saved schema holds unapplied changes, and deploy_production handles production when staging matches production. It also gives concrete when-not conditions (409 refusals) and instructions for retry.

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