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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds nothing beyond the URL — no return shape, pagination, or scope information — and the duplicated sentence wastes space rather than adding behavior detail.

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 string appears verbatim twice, which is pure redundancy, and there is no front-loaded explanatory sentence. It is short but only because content is missing, not because it is efficient.

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?

Two parameters, a nested untyped query object, 0% schema coverage, and no output schema — the description should carry this burden but instead defers entirely to describe_operation. An agent cannot call this correctly from the description 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 nested query/params objects are undocumented. The description says nothing about contractId or the free-form query object; the pointer to describe_operation is the only compensating hint, and it offloads rather than explains.

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 is only the raw route 'GET /api/accounting/contracts/:contractId/payment-schedule' repeated twice, from which an agent can infer it fetches a contract's payment schedule. There is no plain-language statement of the verb+resource, and nothing distinguishes it from the four sibling 'get_accounting_contracts_by_contractId__*' tools, which are different endpoints on the same resource.

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?

No guidance on when to use this versus the other contract-by-contractId endpoints or find_contracts. The only actionable hint is 'describe_operation provides native request schemas', which directs to a schema lookup tool, not to selection criteria.

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