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 by structured data. The description adds nothing beyond that: no mention of ordering, pagination, time-range scoping, or what an empty audit trail means for a read-only history endpoint.

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 content is short but not concise: the identical route sentence is duplicated verbatim, and the operation hash plus the describe_operation note occupy most of the payload. Nothing is front-loaded to explain the tool's effect, so the size is wasted rather than earned.

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?

This is a nested-parameter, read-only history endpoint with no output schema, no parameter documentation, and annotations that only cover safety. An agent still lacks what the audit records represent, how they are ordered or paginated, and what the untyped 'query' bag accepts — substantial gaps given the complexity signals.

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% for the two parameters, so the description must compensate and does not. The only hint is the ':id' path token, implying the required 'params.id' is a standard-clause identifier; the optional 'query' object (nested, additionalProperties: {}) is left completely unexplained — no mention of filters, paging, or date ranges.

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 essentially a restatement of the name and title: it repeats the raw HTTP route 'GET /api/standard-clauses/:id/audit' twice and adds an opaque operation hash. It never says what an 'audit' for a standard clause contains (change history? version events? actor timestamps?), so an agent cannot distinguish it from siblings like get_standard_clauses_by_id_1494be76578086d1e4520500 beyond the literal URL suffix.

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 statement of when to call this versus the plain standard-clause getter or the contracts/leases audit-log siblings. The only actionable pointer is that 'describe_operation provides native request schemas', which routes the agent to another tool for schema discovery rather than explaining selection criteria.

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