retrieve_a_schema

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

Annotations already declare readOnly and idempotent. The description adds the HTTP method (GET), states 'Fetches data. Makes no changes', and explains the behavior of the showFields parameter (e.g., deleted fields show 'status: marked_for_deletion'). No contradictions.

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 description is fairly concise with two main parts: a header and a usage tip. There is slight repetition of 'Retrieve a schema' but overall it is well-structured and not overly verbose.

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?

For a simple retrieval tool, the description covers the main behavior and parameter usage. However, it lacks details about error responses, output structure (no output schema), or edge cases. Adequate but not exhaustive.

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 a usage tip for showFields but does not add new semantic meaning beyond the schema descriptions. For the id parameter, no additional context is provided.

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 retrieves a schema by ID. The verb 'retrieve' and resource 'schema' are specific, and it distinguishes from sibling tools like list_all_schemas (list all) and create/update/delete schemas.

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 includes a usage tip for the showFields parameter but does not provide guidance on when to use this tool versus alternative tools like list_all_schemas. Basic usage is implied but no explicit when-to-use or when-not-to-use.

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