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 fully covered elsewhere. The description adds nothing on return shape, pagination, or filtering behavior – no value beyond structured fields.

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?

Two sentences, but the endpoint path is duplicated verbatim, which is pure waste. The useful content (operation ID and the describe_operation pointer) is buried after the repetition rather than front-loaded.

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 nested-object parameter schema with zero coverage and no output schema, the description should explain at least what the endpoint lists and how to filter. Instead it defers entirely to describe_operation, leaving an agent unable to call the tool meaningfully from this definition alone.

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 two parameters are opaque nested objects ('query' with free-form additionalProperties and an empty 'params' object). The description does not name a single accepted query key or filtering option, offering only a vague pointer to describe_operation. This is well below the baseline that high schema coverage would grant.

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 only restates the endpoint path and title ('GET /api/redline-documents' twice) without saying what a 'redline document' is, what fields are returned, or how it differs from siblings like get_redline_documents_team_members or the negotiation document tools. It is a tautology of the name and title. An agent learns nothing beyond the HTTP verb.

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 alternatives such as get_negotiation_documents_by_documentId or get_contracts_by_id_documents. The only routing hint is that 'describe_operation provides native request schemas', which points to a schema-discovery sibling rather than explaining when to use this tool.

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