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

With annotations only covering safety hints, the description carries the key operational facts itself: the tool is not implemented, returns a notice, is not 'Shop-Graded', and costs 0 MESH/call. It does not reconcile the readOnlyHint=false annotation with a tool that performs no operation, which is a minor residual 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 critical fact (RESERVED — not live) is front-loaded and the alternative routing follows immediately, so the reader is triaged fast. Some bracketed meta ('0 MESH/call, a tool · media') and the restated title add minor noise.

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 placeholder with a single opaque parameter and no output schema, the description supplies everything an agent needs: it is not callable, why, and which live tools replace which sub-capability. Nothing actionable 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%, so the schema already documents the single 'input' payload and its capability-specific shape. The description adds no parameter-level detail, which is acceptable at full coverage but leaves the baseline score.

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 the slot is (a reserved, not-live image/OCR/vision placeholder), what happens on invocation (a not-implemented notice), and explicitly distinguishes itself from live siblings grok-image and grok-image-hq. An agent can tell instantly this is not a callable capability.

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 explicit when-not-to-use guidance ('no provider behind this slot') and names the correct alternatives for the one superseded sub-capability ('use grok-image or grok-image-hq for image creation'), while noting OCR/vision still have no substitute. Routing is unambiguous.

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