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

The read-only annotation is consistent with the 'List' action. The description adds valuable context beyond the annotation by disclosing two behavioral facts: it is free and requires no session, which addresses cost and authentication concerns.

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 single sentence that efficiently conveys purpose, cost, and session requirement. It is front-loaded with the action (List) and contains no filler or redundant information.

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 no-parameter, read-only listing tool with no output schema, the description is complete. It covers what the tool does, pricing/payment info, and access constraints (free, no session), so no additional information is needed.

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?

With zero parameters, the schema provides no input semantics to clarify. The description appropriately omits any parameter discussion, and the baseline for no-parameter tools is 4.

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 uses the specific verb 'List' and clearly identifies the resource: every scrape402 tool, its price, and payment method. It distinguishes itself from sibling tools by being the meta-listing tool rather than a specific function.

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 implies when to use this tool (to discover tools and prices) and adds context that it is free and requires no session, suggesting it's an entry point. It does not explicitly state when not to use it or name alternatives, 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.