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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds 'Writes nothing' to reinforce this. More importantly, it discloses output behavior beyond any structured field: CSV produces one row per entry, while Markdown produces per-asset sections with total spend and next due date. It also surfaces the Pro feature distinction for Markdown, which is useful entitlement context.

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 description is three short sentences with no filler. The core action and range filter are front-loaded, the two format variants are logically separated, and the final 'Writes nothing' reassures without bloating the text. Every sentence earns its place.

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-only export tool with no output schema, the description explains exactly what the agent and user should expect from each format, including structure, aggregation, and Pro restrictions. Combined with a fully described schema and strong annotations, nothing critical is missing for correct invocation and result interpretation.

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%, so the schema alone fully documents all three parameters (to, from, format). The description does not add parameter-level syntax or constraints beyond what the schema provides; it only describes format outcomes, so the baseline of 3 is appropriate.

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 opens with 'Export maintenance entries dated inside a range,' naming a specific verb, resource, and date-scoping. It then distinguishes the two output formats, and the tool name/title reinforces the export function, making it clearly different from siblings like maintenance_log or maintenance_due.

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 description gives clear usage context: CSV is 'ready for a spreadsheet' and Markdown is 'ready to paste into notes or a report,' so an agent knows which format fits which scenario. It does not explicitly mention when not to use the tool or point to alternative siblings like maintenance_log, but the context is sufficient for a straightforward export operation.

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