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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, which is a slightly odd profile for a no-op slot. The description adds the crucial behavioral fact annotations cannot convey: there is no backend and calls return a not-implemented notice. It does not say whether any quota/MESH is actually consumed despite the '(0 MESH/call)' tag, a minor gap.

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 key status ('RESERVED — not live yet') and the routing targets are front-loaded, and the whole thing is one compact block. It is somewhat redundant, restating 'placeholder'/'not live'/'not Shop-Graded' across clauses and appending pricing metadata that is not needed to make the routing decision.

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 deprecated, no-op signpost tool with full schema coverage and no output schema, the description contains everything an agent needs: it is not live, do not call it, and here is where to go instead. Nothing material 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 100% and the single 'input' object is documented in the schema, so the baseline is 3. The description adds nothing about the capability-specific payload beyond the schema's own examples, which is acceptable for a dead routing signpost.

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 states exactly what this tool is (a reserved, not-live placeholder with no provider behind it) and immediately names the two live replacements, grok-tts and grok-stt. An agent can distinguish it from every sibling, including the near-identically named grok-tts/grok-stt lanes, 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?

It gives an explicit when-not-to-use ('SUPERSEDED', 'not live yet', 'calls return a not-implemented notice') and an explicit alternative for each capability ('use grok-tts for text-to-speech and grok-stt for speech-to-text'). Routing guidance is unambiguous.

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