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

The description encourages the agent to 'Try one of the sample questions now', implying the tool will answer these questions. However, the input schema shows the question parameter is only 'echoed back', so the tool returns public metadata rather than executing a query. This is a behavioral discrepancy not covered by annotations; it states a free price but also says 'FREE preview' without explaining the distinction.

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 overlong and overloaded with promotional language ('✅', 'call this now', 'try one of the sample questions now'), price details, and sample content. The functional purpose is buried in the sales copy, making it inefficient for an agent to parse.

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?

Without an output schema, the description needs to at least say what the tool returns. It doesn't mention that the preview contains only 'public metadata' or that the question is echoed. An agent is left unsure whether the result will be a listing, a message, or merely confirmation.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds example questions for the 'question' field but does not clarify the 'slug' parameter or the fact that 'question' is only echoed. This does not meaningfully go beyond the schema's own descriptions, so baseline is appropriate.

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 tells the agent to call now and lists sample questions, but it never clearly states that the tool provides a free preview of a listing's public metadata. The action is only implied by the tool name and the annotation title, not by the description itself.

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 about when to use this tool vs. the sibling tools, such as data_session_query. It says 'No API key needed' and 'call this now' but doesn't explain the circumstances under which the free preview is appropriate or when another tool should be chosen.

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