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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint, which already cover safety. The description adds 'No API key needed' and 'FREE preview,' but does not disclose what happens when called (e.g., return format, pagination, or any side effects). It adds minimal behavioral context beyond 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 a run-on promotional pitch with emojis, pricing, and sample questions. It is not concisely structured for technical consumption; the key functional information is buried under marketing fluff.

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 simple 2-parameter tool, the description lacks essential information about what the preview actually returns. The schema mentions 'public metadata only,' but the description does not, so an agent has no clear picture of the output. It is incomplete despite low complexity.

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 100%, with descriptions for both slug and question. The description mentions sample questions, which partially relates to the question parameter but does not explain slug or provide additional parameter-specific guidance. Baseline 3 is appropriate given high schema coverage.

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 is promotional rather than technical. It says 'FREE preview' but does not clearly state what the tool does beyond implying a preview of a listing. It mentions the listing name and sample questions but lacks a specific verb+resource that distinguishes it from 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?

There is no guidance on when to use this tool versus alternatives. It simply urges 'call this now' without any context about selection criteria or exclusions. Sibling tools exist but are not referenced.

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