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

With no annotations, the description carries the disclosure burden. It explicitly states the operation is read-only, free, and spends nothing, and it explains the verified-only filtering behavior. This goes well beyond the schema.

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?

Three compact, information-dense sentences. The core purpose is front-loaded, and every sentence adds operational value without fluff.

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?

Adequate for a read-only search tool. It covers what is searched, the filtering default, and the safety profile. It does not describe the return shape, but the absence of an output schema is a minor gap for a simple search result list.

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?

The description clarifies what the query parameter matches (listing name, description, category, provider name) and confirms how verified_only changes results, supplementing the schema. Limit is not described, but its schema constraints make it self-explanatory.

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 ('search'), resource ('live catalogue'), and searchable fields (name, description, category, provider name). Clearly distinguishes itself from siblings: this is free-text search, not retrieval of one API or a plain list.

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?

Makes the intended use obvious: free-text queries over the catalogue. It does not explicitly name get_api/list_apis as alternatives, but the framing is clear enough that an agent can select it appropriately for keyword-style lookups.

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