search_gp_tools

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

Discloses search behavior: terms ANDed, matched against tool names, empty query lists everything up to limit. No annotations provided, so description carries burden; lacks mention of any side effects but search is harmless.

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 concise sentences with clear structure: purpose then usage details. No unnecessary words.

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?

Given simple parameters and presence of output schema, description covers essential usage: how to query and what happens with empty query. Fully adequate for agent invocation.

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?

Without schema descriptions (0% coverage), description implies query and limit parameters but does not explicitly define them or their defaults/ranges. Adds some value beyond schema names but not fully compensatory.

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?

Clearly states it searches all available geoprocessing tools including extension toolboxes, distinguishing it from siblings like run_gp_tool and describe_gp_tool.

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 clear guidance on query syntax (space-separated ANDed terms), name matching example, and empty query behavior, but does not explicitly compare to alternatives.

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