wafeq_revenue_recognitions_end_early_create

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

Beyond the destructiveHint annotation, the description adds critical behavior: posting to the ledger, irreversibility, no API undo, and whole remaining balance recognition. This gives the agent a full safety picture before invocation.

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 compact, front-loaded with the irreversible warning, and every sentence contributes either safety context, endpoint clarification, or a preview recommendation. No filler.

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 destructive, irreversible action with no output schema, the description provides the essential context: what the tool does, the ledger impact, the absence of undo, and the required preview step. Combined with the schema, an agent has enough to invoke it correctly and safely.

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 schema already documents amount, end_early_date, end_early_account, notes, and start_date. The description adds context by mentioning the 'provided account' and 'remaining balance', but it doesn't fully compensate for the remaining 50% schema coverage gap, especially around id and the body object semantics.

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 states a specific verb and resource: it terminates a revenue recognition early and recognizes the remaining balance immediately. This clearly distinguishes it from the preview sibling tool by framing it as the actual posting action.

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 tells the agent to run the matching preview_... tool first to see what would be posted, which is strong usage guidance. It also warns that there is no API undo. It doesn't enumerate every alternative or exclusion, but the preview-before-execute instruction is clear and actionable.

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