describe_geoprocessing_tool

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

With no annotations, the description carries the behavioral burden and does so reasonably: 'Get' and 'before running it' signal a read-only, non-executing metadata lookup. It does not explicitly state that no side effects occur or describe auth requirements, but for this tool type the read-only implication is strong and accurate.

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?

It is a single front-loaded sentence with no wasted words. Every element—verb, returned metadata categories, and timing relative to execution—earns its place.

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 a single parameter, full schema coverage, and an existing output schema, the description is complete enough for correct selection and invocation. It states what metadata is returned and when to call it; no further detail is needed for this low-complexity tool.

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 coverage is 100% and the single parameter tool_name already includes an example format, so the schema does the necessary work. The description adds no further parameter semantics beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb ('Get') and resource ('a tool's parameters, data types, defaults and usage text'), making the purpose immediately clear. The phrase 'before running it' distinguishes this metadata-retrieval tool from execution siblings such as run_geoprocessing_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?

The description explicitly says to use it 'before running it,' which gives a clear usage context relative to execution tools. It does not name an alternative tool or give a when-not condition, but the timing guidance is sufficient for this simple describe operation.

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