List AINumbers tools

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds valuable behavioral context: it returns deep-links and explains prefill-enabled tools accept a specific query parameter format for one-click invocation. This goes beyond 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 two sentences long, front-loaded with the main purpose. However, the second sentence focuses on a technical detail about prefill links, which may be less relevant for initial tool selection, slightly reducing effectiveness.

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 three parameters and no output schema, the description should provide more context. It does not describe parameter usage, result structure beyond 'deep-links', pagination, or limits. The tool is under-described given its complexity.

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 parameter descriptions have 0% coverage. The description does not explain any of the three parameters (query, category, limit). Without this, the agent cannot infer what values to provide or how they affect results. The description fails to compensate for the schema gap.

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 states the tool's purpose: 'Search the AINumbers catalog (420 client-side fintech tools).' The verb 'search' and resource 'catalog' are specific, and the tool is distinct from all sibling tools, which focus on different domains like sandbox, AML, auditing, etc.

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 mentions when to use (to search catalog) but does not explicitly state when not to use or suggest alternatives. No exclusions or context comparisons are provided, leaving the agent to infer usage from purpose alone.

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