search_pdb

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

No annotations are provided, so the description carries full burden. It only reveals that the search is 'live' and uses 'literal text', but does not disclose matching behavior (e.g., case-sensitivity, substring vs whole-word), result format, or behavior of the limit parameter.

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?

A single, front-loaded sentence that states the action and key constraint with no wasted words. It is appropriately minimal and scannable.

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?

The tool has a simple interface and an output schema, but the description omits usage context and behavioral details (e.g., how matching works, how limit affects results). It is minimally viable but leaves gaps that an agent would need to discover at runtime.

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 0%, and the description only hints at query semantics via 'literal text'. The 'limit' parameter is not explained at all, and no additional meaning is added beyond the raw schema.

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?

Description uses a specific verb ('Search'), identifies the resource ('live GIMP PDB procedure names'), and clarifies the method ('by literal text'). This clearly distinguishes it from sibling tools like describe_pdb_procedure and invoke_pdb_procedure.

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?

No explicit guidance is given about when to prefer this over describe_pdb_procedure or invoke_pdb_procedure. The description implies its role as the search entry point but lacks any when-to-use or exclusion details.

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