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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes well beyond them: it names exactly what loses data (tables, fields, entities, relationships), discloses async behavior with job_id polling via get_job_status, and documents both refusal modes (concurrent operation naming the running job, and RationalBloks maintenance). This is the burden-carrying detail an agent needs before an irreversible call.

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-loads the destructive warning and the intent condition, then handles async, concurrency, and maintenance in discrete, scannable statements. It is long, but nearly every clause carries an operational constraint; only the environment restatement duplicates 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?

With no output schema, the description still covers the return contract (poll job_id with get_job_status) and the failure paths. For a two-parameter destructive mutation tool, an agent has everything needed to decide, invoke, and follow up correctly.

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%, so both parameters are already documented in the schema. The description's restatement of the environment values (staging deploys the saved schema, production promotes staging) mirrors the schema text rather than adding new meaning, so the baseline 3 applies.

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 ('Deploy a plan that drops data') plus scope ('relational or a graph project'), and the title/description immediately distinguish it from the non-destructive deploy siblings. An agent can tell this apart from deploy_staging/deploy_production without opening any 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?

Explicit when-to-use: only after a deploy tool (deploy_staging, deploy_production, deploy_graph_staging, deploy_graph_production) refused the plan, naming its drops, and those drops are intended. It also names the environment semantics and the concurrency/maintenance refusals to expect. Nothing is left to inference.

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