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

Annotations already declare the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false), so the description only needs to add context. It adds the accepted input formats, which is genuinely useful, but says nothing about duplicate handling, validation failures, or what a rejected report looks like — notable given the non-idempotent flag.

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?

A single front-loaded sentence with no filler; the accepted formats are packed into the same clause rather than padded into a second paragraph.

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 non-idempotent write with four parameters and no output schema, the description covers input format but omits the outcome: whether an imported report returns an ID, whether re-imports are rejected or duplicated, and whether the report is parsed synchronously.

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 coverage is 75% with only 'filename' undocumented. The description earns credit by explaining the choice between the two content parameters — raw XML versus base64 of a .xml/.gz/.zip — which the schema does not disambiguate. It does not clarify the semantics of filename.

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?

States a specific verb (import) and a specific resource (DMARC aggregate report), plus the accepted encodings. The word 'aggregate' implicitly separates it from the forensic-report siblings, though no sibling is named outright.

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 guidance on when to use this versus get-dmarc-report or list-dmarc-reports, no prerequisite that the domain must already exist, and no statement about what to do when a report has already been imported.

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