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

Annotations already establish readOnlyHint and non-destructive behavior. The description adds useful, non-redundant operational details: no API key required, price per query, max 20 queries/session, and that it is a guest callable preview. No contradiction with 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 padded with repeated marketing language: 'No API key needed', 'FREE preview', 'no key, no payment', and 'Try one of the sample questions now'. It is long and promotional without first stating the tool's purpose.

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?

There is no output schema, so the description should explain what the preview returns, but it only provides pricing, quotas, and example questions. An agent can guess it returns sample data, but the response format remains unspecified.

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?

The input schema already fully describes both optional parameters, so the baseline is 3. The description gives concrete sample questions that could guide the `question` parameter, but it never explicitly links them to the parameter names, and `slug` is not explained beyond what the schema already says.

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 says 'FREE preview' but never clearly states what the tool does or what it returns. It is dominated by a specific listing, pricing, and sample questions; the actual functional purpose is left mostly to the title and the schema description.

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 for when to use this tool versus siblings like data_session_query, a2awire_guide, or find_paid_work. 'Call this now' is an instruction, not a usage decision criterion.

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