get_schema

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

With no annotations provided, the description carries the full burden. It discloses the output format options (brief/detailed/full), the default, and behavior for unknown names ('reported under 'Tools not found''). It does not explicitly state read-only safety, but this is strongly implied by the action of getting schemas.

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?

Three concise, front-loaded sentences. First sentence states purpose, second gives usage context, third lists output modes and edge-case behavior. Every sentence earns its place with no redundancy.

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?

The tool is simple (2 params, one enum) and the description covers use case, output formats, and not-found handling. An output schema exists, so return values don't need description. It is complete and self-sufficient.

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%, so baseline is 3. The description adds meaningful behavioral detail beyond the schema, particularly that unknown names are reported under a 'Tools not found' section and that 'detailed' yields markdown parameter schemas per tool. This enriches understanding of both parameters.

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 tool's function: 'Get parameter schemas for named tools before calling them via execute.' It uses a specific verb and resource, and distinguishes itself from siblings by explicitly saying 'Not for discovery — use search for that.'

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 explicit when-to-use guidance: 'when you already have tool names (from search or tags) and need exact parameters' and an explicit exclusion: 'Not for discovery — use search for that.' This fully clarifies context versus alternatives.

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