gimp.procedure.search

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

With no annotations, the description must disclose behavioral traits. It mentions searching by name or help text, which is useful, but does not describe output format, pagination, case sensitivity, or whether regex is supported. The schema hints at regex, but the description itself is limited.

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?

Two sentences with no superfluous words. The first states the action and criteria; the second adds context as an entry point. Every sentence serves a purpose.

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?

For a simple search tool with no output schema, the description is functional but incomplete. It lacks details about what the search returns (e.g., list of procedure names) and how to use results with sibling tools like gimp.procedure.describe. The limit parameter is also unexplained.

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 50%; only 'query' has a description. The tool description adds context for 'query' by noting it searches name/help text, but it does not explain 'limit' (default, range, or purpose). Thus it partially aids understanding but not fully.

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 verb 'Search' and the resource 'GIMP's Procedure Database', and specifies the criteria ('by name/help text'). It also positions itself as the discovery entry point, distinguishing it from sibling tools like gimp.procedure.describe or gimp.procedure.call.

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 indicates this tool is the entry point for discovering procedures, implying it should be used before describe or call. However, it does not explicitly state when not to use it or list alternatives, leaving some ambiguity.

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