Get a tool's input schema

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

Annotations already cover read-only, idempotent, non-destructive safety, but the description adds important behavioral details: the returned JSON structure, that notes are app rules to follow, and that the file must not be cached because the app rewrites it when its schema version changes.

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?

The purpose is front-loaded and the remaining details are structured around return fields, echo/notes semantics, and caching. It is somewhat detailed for a one-parameter tool, but most sentences carry useful information.

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?

With no output schema, the description adequately explains the returned schema object, including fields, echo, notes, and the no-caching rule. It gives an agent enough context to call this read-only tool correctly.

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?

The single tool parameter is fully documented in the schema with enum values. The description adds only general context that it selects one tool, so it does not extend parameter meaning beyond the schema baseline.

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?

States a specific verb and resource: return the schema file for one tool, described as the blank input form. It also differentiates from sibling setoolbox_run by instructing the agent to read it before every run.

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?

Explicitly says to read it before every setoolbox_run and to use only the field names and units it lists. It also gives a caching constraint across app launches, though it does not name when-not-to-use alternatives beyond the run dependency.

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