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 without the description. The description adds nothing behavioral beyond the schema-lookup hint — no mention of pagination, filtering, response shape, or rate limits.

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?

Very short, but the first sentence is duplicated word-for-word and the remainder is a bare operation ID, so there is no front-loaded useful content. Brevity here reflects under-specification rather than efficiency.

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 read endpoint with free-form nested query objects, no output schema, and 0% parameter documentation, the description leaves an agent unable to know what filters to pass or what comes back. The describe_operation pointer is the only lifeline, and it forces a second round-trip.

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 ('query' and 'params') are untyped free-form objects with additionalProperties, so the schema explains nothing. The description does not compensate at all — it never mentions what query keys are accepted or what 'params' is for.

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 the tool name and HTTP path repeated verbatim ('GET /api/accounting-books. GET /api/accounting-books.'), which restates the title rather than explaining what an 'accounting book' is or what the response contains. The only added information is an opaque operation ID, which does not help an agent understand purpose.

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?

The single usable signal is 'describe_operation provides native request schemas', which hints at a prerequisite lookup, but there is no statement of when to call this versus the dozens of sibling accounting endpoints (account mappings, contracts, journal entries, GL accounts). No exclusions, no context conditions.

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