Shop info

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: output is plain text, and order-specific shipping costs cannot be quoted without a logged-in address, so the agent should quote general rules. It stops short of describing pagination or page-selection behavior.

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?

Front-loads the core action, then the use cases, then the shipping caveat and fallback sibling. Every sentence earns its place with no filler.

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?

With rich annotations, a fully documented enum parameter, and an output schema covering return values, the description supplies everything else an agent needs: what it returns (plain text), when to use it, and when to route elsewhere.

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% with a single fully documented enum, so the schema already carries the parameter meaning. The description restates the topic areas but adds no enum syntax or format detail beyond what the schema provides, making the baseline 3 correct.

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?

States a specific verb and resource ('Read one of Technolife's info pages as plain text') and enumerates the covered topics (stores, shipping, returns, payment). It explicitly distinguishes itself from the sibling tl_faq, so an agent can route between them without opening either schema.

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?

Gives explicit when-to-use triggers ('questions about physical stores, how and how much shipping costs per city, returns and how to pay') plus a key caveat that exact order shipping needs a logged-in address, and names the alternative (tl_faq) for other questions. This is near-complete routing guidance.

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