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 elsewhere. The description adds nothing beyond restating 'GET' and pointing at describe_operation: no pagination, filtering defaults, result ordering, or response shape is disclosed for a collection endpoint that likely paginates.

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 core sentence 'GET /api/recon-docs/audit-packages' appears twice back to back, which is pure waste, and the operational ID adds no decision value. The description is short but poorly structured rather than 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?

For a two-parameter, nested-object collection endpoint with no output schema and 0% schema coverage, the description should explain what the query object accepts and what the listing returns. Instead it delegates entirely to describe_operation, leaving the agent unable to construct a call without a second tool hop.

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 'query' parameter is an unconstrained object with additionalProperties {}, so the schema tells the agent nothing about supported filters. The description does not compensate at all — it neither names any query fields nor explains what 'params' is for, only deferring to describe_operation.

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 names the verb and resource (GET /api/recon-docs/audit-packages), so the agent knows it lists audit packages, but the same sentence is repeated verbatim and never explains what an audit package is or what the listing contains. It implicitly distinguishes itself from the sibling get_recon_docs_audit_packages_by_id, but only through the URL rather than explicit routing language.

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 use this list endpoint versus the by-id sibling, no prerequisite or scope conditions. The only usable guidance is the pointer that describe_operation provides native request schemas, which is about schema discovery rather than tool selection.

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