search_arcpy_tools

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

With no annotations, the description carries full behavioral burden. It adds useful details: tools are 'callable', limited to this ArcMap 10.8 runtime, and result count is capped at 500. It does not disclose query matching behavior or potential return/error behavior, though the output schema partly covers return structure.

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 with no filler. Every phrase adds signal: search, callable tools, runtime scope, and result cap.

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?

This is a simple discovery tool and the output schema likely covers return values, but with no annotations and minimal parameter guidance, the definition leaves important usage semantics unstated. It is adequate but not complete for an agent deciding how to query and use results.

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?

Input schema has 0% description coverage and the description does not explain the 'query' parameter at all; 'limit' is only indirectly addressed by 'up to 500'. The agent cannot tell whether query matches tool names, aliases, metadata, or supports wildcards.

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 names a specific action ('Search'), a precise resource ('callable ArcPy GP tools installed with this ArcMap 10.8 runtime'), and a bound ('up to 500'). This makes it clear the tool is for discovery rather than execution, distinguishing it from siblings like run_geoprocessing.

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 intended context is implied: use it to find ArcPy GP tools available in this runtime. However, it never explicitly says when to choose this over run_geoprocessing or run_advanced_geoprocessing, nor gives any when-not-to-use guidance.

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