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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds value by disclosing that requests are authenticated and by pointing to the per-group swagger docs for full request/response schemas, which the annotations cannot express.

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 sentences with no filler: capability first, discovery mechanism second, schema reference third. The long docs URL is functional content, not padding.

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 generic pass-through tool with no output schema, the description covers what it does, how to find valid inputs, and where return shapes are documented. It stops short of stating error behavior or whether the response is passed through verbatim, which keeps it from a 5.

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 the baseline is 3; the description earns an extra point by telling the agent that the authoritative definition of valid paths and query parameters lives in the group-specific swagger page. That directly helps populate the free-form 'query' object, which the schema only types generically.

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 ('Issue an authenticated GET request to any DirectIQ endpoint') and the word GET immediately distinguishes it from the sibling directiq_write_request. The escape-hatch nature for endpoints without a dedicated tool is explicit.

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?

Names the precondition for use ('GET operations that have no dedicated tool') and routes the agent to directiq_list_endpoints to discover valid (group, path) pairs. This implicitly and clearly excludes endpoints already covered by the many dedicated siblings like directiq_get_contact.

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