reconcile_period

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

Annotations declare openWorldHint=true, meaning the tool may interact with an open world of external entities, yet the description emphatically states it is composed 'entirely from Manager's own transaction data (no external system is consulted)'. This directly conflicts with the annotation, constituting an annotation contradiction.

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?

Three tightly packed sentences with the read-only, period, and data-source facts front-loaded. Dense but each clause carries signal; the em-dash caveat about non-fabricated totals is well placed and earns its space.

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?

An output schema exists so return values need not be described, and the description adds useful output-quality context (exception Manager Keys, raw feeds, explicit notices instead of fabricated totals). However, it omits any usage framing and leaves the date parameters unexplained, so it is only minimally complete for a report 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 two date parameters (from_date, to_date) are documented at 0% schema coverage, so the description must carry their meaning. 'PERIOD' weakly implies date-range filtering, but no format, semantics, or default behavior of the parameters is explained, leaving the schema and description jointly inadequate.

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+resource, the 'Read-only PERIOD reconciliation report,' and clarifies its data provenance (Manager's own transactions). An agent can tell it produces a period-scoped reconciliation, though it never names or distinguishes itself from close siblings like trial_balance or the reconstructed_* family.

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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. The word 'PERIOD' hints that a date range selects this tool, but nothing tells the agent why to prefer it over ledger_transactions, trial_balance, or the reconstructed reports.

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