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

Annotations already mark the tool as read-only and idempotent, but the description adds substantial behavioral detail beyond them: exact deployment statuses, failure interpretations, troubleshooting steps, and the fact that staging.url/production.url/github.url are returned. It also reveals that create_project lacks URL return, which clarifies this tool's unique value. No contradiction with 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 longer than average but every sentence earns its place: purpose, statuses, troubleshooting, return-value behavior, and when-to-use guidance. It is front-loaded with the core purpose and uses clear section labels (DEPLOYMENT STATUS, TROUBLESHOOTING, RETURNS) that make it easily scannable for an agent.

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?

Given there is no output schema, the description compensates by explaining key return fields (staging.url, production.url, github.url) and covering status semantics and failure diagnostics. The tool has a single required parameter, and the description gives enough context for an agent to call it correctly and interpret the result.

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% for the single parameter project_id, which is already documented as a UUID. The description does not add parameter-specific meaning beyond what the schema provides, but it doesn't need to; the baseline of 3 applies since the schema carries the full parameter information.

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 opens with a specific verb and resource: 'Get detailed project info including deployment status and resource usage.' It clearly distinguishes from create_project by noting that create_project does NOT return a URL and that this tool is the one to call after deployment. The scope is concrete and unambiguous.

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?

The description explicitly states when to use this tool: 'create_project does NOT return a URL, so this is the tool to call once get_job_status reports the deployment finished.' It also guides troubleshooting by directing the agent to 'Use get_schema to review current schema' when CrashLoopBackOff occurs. This is clear usage guidance with named alternatives.

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