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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context beyond those annotations: authentication is not required, there is a 0.01 USDC/query cost context for the listing, there is a 20-query/session cap, and the tool targets the bleepingwatch listing specifically.

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 repetitive and promotional: 'FREE', 'no key', 'no payment', and 'call this now' appear multiple times. The useful facts are present but padded with marketing language, emojis, and redundant encouragement, making it less efficient than it could be.

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 read-only preview tool with two optional parameters, the description is mostly adequate: it states cost, auth, session limits, and sample questions. However, with no output schema, it should explicitly say what the agent will receive back (e.g., public metadata or a sample answer) and ideally point to the paid query sibling for full access.

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 both parameters (slug and question) are already well documented, including defaults and the echoed-back behavior. The description adds sample questions that illustrate the question parameter, but it does not add meaning for the slug parameter or clarify how to target a different listing.

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 clearly identifies this as a free preview of a specific data listing (bleepingwatch) and invites the agent to call it with sample questions. It stops short of stating the exact operation and return value, and it does not explicitly differentiate itself from sibling tools like data_session_query, but the free-preview intent is unmistakable.

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 description gives strong when-to-use guidance: no API key needed, no payment required, and the agent should call it now and try sample questions. It does not mention when to prefer a paid sibling like data_session_query or data_session_open, so exclusions and alternatives are missing, but the context is clear.

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