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

The description discloses a critical behavioral trait the annotations do not: the tool is not implemented and refuses. That is exactly the kind of context annotations cannot carry. However, the annotations declare destructiveHint=true and idempotentHint=true, which imply a real mutation occurs, conflicting with 'this refuses'.

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?

Three short sentences, front-loaded with the verb and the blocking fact, then the remediation. Every sentence earns its place with zero filler.

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 non-implemented no-op with no output schema, the description is complete: it states the tool refuses and gives the correct alternative paths. Nothing an agent needs to avoid a wasted call is missing.

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% and the description says nothing about project_id or idempotency_key. project_id is inferable from the tool name, but idempotency_key is entirely undocumented in both schema and description. Since the tool refuses anyway, the practical impact is low, but no meaning is added.

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+resource ('Stop the project') and immediately qualifies it with 'NOT IMPLEMENTED: the platform has no stop, and this refuses.' An agent can tell exactly what this tool is (a no-op) versus the real service-removal siblings.

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?

Explicitly says when NOT to use it and names concrete alternatives with their conditions: 'delete_project it or take its domain off with delete_domain.' This is a textbook routing instruction with no inference required.

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