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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no further behavioral context such as what the response contains, whether results are paginated, or any auth/permission requirements. It does not contradict the annotations, but it contributes nothing beyond them.

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 same endpoint sentence appears twice verbatim, wasting space, and the operation ID / describe_operation pointer are tacked on. It is short but not front-loaded with any purpose statement.

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?

No output schema exists, and the description does not explain the return shape (the available fields) or how to query them. For a listing endpoint with an unconstrained free-form query object, the description is far too thin for an agent to call it 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?

Schema description coverage is 0% and the description says nothing about the two parameters (a free-form 'query' object and an empty 'params' object). With nested/free-form input and no documentation of valid query keys anywhere, the description provides zero parameter meaning.

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 repeats the raw endpoint path 'GET /api/check-request-templates/available-fields' twice without stating in plain language what it returns (e.g., 'List the fields available for check request templates'). An agent can infer a resource from the path, but it is essentially a tautology of the name/title and does not differentiate this from sibling tools like get_check_request_templates_38069a382fe0c4228a46178c.

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?

There is no guidance on when to call this versus the many sibling get_check_request_templates tools. The only actionable hint is 'describe_operation provides native request schemas,' which is a workflow pointer, not a when/when-not rule for this tool.

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