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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds the auth prerequisite (connected Aurgus account), tenant scoping, and that all figures are computed off the canonical ledger. It does not disclose the delivery mechanism — whether the call returns a file, a download URL, or inline structured content — which is the key unknown for a tool named 'export'.

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 deliverable is front-loaded in the opening clause, which is good. But the single run-on sentence is padded with marketing phrasing ('the open accrual you can stand behind', 'where margin is leaking') and em-dash nesting, when a plain enumeration of the package contents would read faster.

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?

With no parameters and no output schema, the description carries the burden of describing results, and it does partially substitute for an output schema by enumerating the three package components. It still omits output format, size/timing expectations, and any hint about how the result is retrieved, which leaves real gaps for an export-style tool.

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?

The tool takes zero parameters, so the baseline is 4; the empty schema (additionalProperties: false) leaves nothing for the description to explain. The description implicitly confirms there is no period/tenant argument to supply, since scope is fixed to 'your tenant'.

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 concrete deliverable (auditor-ready package containing open accrual, margin leakage vs. off-program spend, and sample lineage) and its data source (canonical ledger), which is far more specific than the bare name 'export'. However, it never distinguishes itself from the closely related sibling 'export_workpapers', nor from 'report'/'run_report', so an agent cannot tell which export to pick from the description alone.

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 only usage-adjacent content is the prerequisite 'Requires a connected Aurgus account'. There is no statement of when this tool should be chosen over export_workpapers, report, or run_report, and no exclusions or timing cues (e.g., period close, audit request).

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