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

Annotations already cover readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is known. The description adds genuinely new behavioral context: the exact result fields, the price.listedOnly caveat about shipping/tax at checkout, and an explicit prompt-injection warning that seller text is untrusted data. The latter is high-value for an open-world search tool.

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 and the read-only fact, then layers return shape, pricing caveat, and the injection warning. Slightly dense but every sentence carries a distinct piece of information; nothing is redundant.

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 no output schema, the description usefully enumerates the returned fields (title, description, price, shop, rating, pageUrl), which compensates for the absent return spec. Combined with the pricing and untrusted-data notes, it is close to complete for a read-only search, missing only inter-tool routing.

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 all five parameters (kind, shop, limit, query, category, with defaults and constraints) are already documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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: 'Searches products and services listed on GenesisPay.' The scope is clear, though it never explicitly contrasts its search role against siblings like trending or shops, which an agent must infer.

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?

Provides context (purchases happen on genesispay.finance and need an account) but gives no when-to-use guidance relative to genesispay_catalog_trending, genesispay_catalog_shops, or reviews. The agent must infer which tool fits which intent.

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