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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint). The description adds value beyond them by enumerating the fields each mapping record carries, which substitutes for the absent output schema, and by disclosing the underlying POST /reporting/mappings/list endpoint. It does not mention result volume or paging behavior beyond what the schema already documents.

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 compact sentences, front-loaded with the resource and its returned fields. The trailing raw endpoint '/reporting/mappings/list' is low-value filler for an agent but costs little. No redundancy.

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 simple two-param, zero-required list tool, the description plus a full-coverage schema and safety annotations is mostly sufficient, and the field enumeration compensates for the missing output schema. The gap is routing: nothing tells the agent when to list mappings versus calling qgiv_get_report_mapping for a single one.

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 100% and both limit/offset are fully documented in the schema, so the description carries no additional parameter burden. Baseline 3 applies. The unexplained 'on the form(s)' scoping phrase adds slight ambiguity rather than clarity about inputs.

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?

Clear verb+resource: listing report (accounting export) mappings, with the parenthetical expanding the jargon. The returned fields are enumerated (id, identifier, mapping data, export service, type), which sharpens what a 'report mapping' is. It does not explicitly contrast itself with the sibling qgiv_get_report_mapping, though the list/get distinction is inferable.

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 statement of when to use this versus qgiv_get_report_mapping or when listing is preferable to fetching a single record. The phrase 'on the form(s)' suggests a form-scoping filter, but no such parameter exists in the schema, so this hints at context it never explains.

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