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

Beyond the annotations, the description discloses important behavior: deployment creates a separate production instance, requires a paid plan, destructive drops are refused until confirm_destructive=true, only one operation runs per project at a time, and transient 'RationalBloks is being updated' refusals should be retried. This is rich, actionable behavioral context and does not contradict the annotations.

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?

The description is front-loaded with its core purpose, then provides tightly packed, non-redundant operational caveats. Every sentence earns its place: prerequisites, destructive confirmation, concurrency, and transient retry conditions are all material to calling the tool correctly.

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?

Despite having no output schema, the description covers the prerequisite (paid plan), the destructive guard, the one-job-at-a-time rule, and the retry path via get_job_status. An agent has enough information to know when to call it, what may cause refusal, and how to recover.

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 100%, so the schema already documents both project_id and confirm_destructive. The description reinforces the destructive-confirmation semantics ('pass confirm_destructive=true after reviewing the plan') but adds little beyond the schema's own parameter descriptions. 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?

The description uses a specific verb and resource: 'Promote graph staging to production' and adds that it 'Creates a separate production Neo4j instance with its own credentials and database.' This clearly distinguishes it from deploy_graph_staging by direction and from generic deploy_production/deploy_staging by being graph-specific.

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?

It states when to use the tool: when promoting a graph staging environment to production and when the paid plan is available. It also gives practical operational guidance about retrying after a concurrent job finishes or after the RationalBloks update message. It does not explicitly enumerate alternatives or say 'use deploy_graph_staging instead,' so it stops short of a 5.

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