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 fully covered by structured data. The description contributes nothing beyond that — no note on scoping, required permissions, pagination, or what the aggregation covers.

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 same endpoint sentence appears twice back-to-back, which is pure waste rather than front-loaded signal. The remaining clause about describe_operation is the only informative content and could have stood alone.

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 an opaque, untyped aggregation endpoint with nested free-form query objects, no output schema, and 0% parameter documentation, the description should explain what is aggregated and what filters exist. Instead it offers only an operation ID and a pointer to a sibling, leaving the essential contract undefined.

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% for two free-form parameters ('query' accepting arbitrary properties and an empty 'params' object), so the schema provides almost no meaning. The description makes no attempt to describe accepted query fields or filters, only deferring to describe_operation, leaving the caller with no semantic anchor.

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 repeats the URL path 'GET /api/accounting/journal-close/aggregation' twice and adds only an operation ID, which is a tautological restatement of the name and title. It never says in plain language what a 'journal close aggregation' returns (e.g. aggregated close status, balances, or rollups) or how it differs from the many sibling journal-close endpoints such as get_accounting_journal_close_batches or get_accounting_journal_close_runs.

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 when-to-use, when-not-to-use, or sibling comparison is given. The only guidance is a pointer to describe_operation for request schemas, and a generic reference to execute_read is absent entirely, so an agent must infer that this is a read call routed through some other tool.

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