Reopen Accounting Period

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

Annotations indicate destructiveHint=true, and the description adds context about audit logging and backdated edits, reinforcing the behavioral implications. It doesn't contradict annotations and adds value beyond them.

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 concise with front-loaded context ('TRUST AREA — FISCAL REOPEN') and clear sentences. Bilingual content adds some redundancy but is acceptable for the intended use.

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?

The description explains the purpose, required parameters, and warns about consequences. An output schema exists, so return values are covered. It's mostly complete, though prerequisites like 'period must be closed' are implied not explicit.

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 100%, so the description's mention of reason for audit and confirm=true aligns with schema descriptions but doesn't add substantial new meaning. Baseline 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 clearly states 'Reopen a closed accounting period' with a specific verb and resource. It also mentions 'allows backdated edits to invoices/expenses', distinguishing it from the sibling 'period_close' tool.

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 explicitly requires a compliance reason and 'confirm=true', and warns 'use with extreme caution'. It provides clear context for when to use, though it doesn't explicitly list alternatives or when not to use.

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