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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description earns credit by adding behavior the annotations omit: it discloses the accepted ID namespace syntax and the return shape (JSON-text results containing human-readable text), which is valuable given there is no output schema.

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?

One tight sentence, front-loaded with the tool's role and followed by the identifier examples. The phrase 'JSON-text results with human-readable text' is mildly redundant, costing it a perfect score, but there is no 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 single-parameter, read-only alias tool with no output schema, the description covers purpose, ID format, and return shape, and the annotations cover safety. The notable gap is sibling differentiation – it never explains how this relates to the parse_get_* tools it appears to duplicate.

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 coverage is 0% – the schema only says id is a required string. The description compensates by revealing the namespaced identifier pattern (prefix:value) and three concrete examples, which is real semantic value. It is not exhaustive about which prefixes are valid, but it conveys the format well enough to call the tool.

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 names a concrete verb (resolves) and resource (fetch IDs) and illustrates the ID scheme with three examples (brand:stripe, topic:<id>, question:best-crm), so an agent knows what domain this operates on. It stops short of differentiating itself from the many parse_get_* siblings that appear to serve the same entity types.

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 only usage cue is 'compatibility alias,' which hints at legacy status but never states when to prefer this over parse_get_brand, parse_get_topic, parse_get_question, or search. With 28 siblings and no explicit when/when-not guidance, the agent is left to guess.

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