wafeq_revenue_recognitions_preview_end_early_create

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

Annotations already mark readOnlyHint/idempotentHint/destructiveHint, and the description complements them by explaining the semantic oddity of a POST that performs no writes. It explicitly states it returns the events that WOULD be generated and writes nothing to the ledger, which is exactly the kind of behavioral context an agent needs. No 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?

Front-loaded with a READ-ONLY/preview/simulation badge and endpoint, followed by a short explanation and a clarifying note about the POST semantics. Each sentence adds useful signal, though 'Preview early termination' duplicates the annotations/title slightly.

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 read-only preview with no output schema, the description covers what the agent needs: it previews the remaining balance, shows events that would be reversed, and does not mutate state. It does not detail the exact response shape, but the conceptual return is described well enough for selection and invocation.

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 `body`, `date`, and `start_date`, and the endpoint path in the description implies `id` is the revenue recognition identifier. The description adds little parameter-level meaning beyond tying the date to the early termination. With 50% coverage, the missing `id` is trivially inferable, so this is adequate but not enriched.

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 and resource: previewing early termination of a revenue recognition, and describes what it returns (remaining balance and posted events that would be reversed). The 'preview / simulation' label and the explicit 'writes nothing to the ledger' distinguish it from the actual end-early sibling.

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 sets clear context: this is a read-only simulation for previewing the effects of terminating a revenue recognition early. It does not explicitly name `end_early_create` as the alternative or state when not to use it, so it falls short of fully explicit routing. Still, the simulation/writes-nothing framing makes the use case evident.

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