podyx_aftercare_cancellation_preview

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real behavioral context: key authority and stored tenant ownership apply, customer vs staff policy differences, acceptance freezing the target/selection, provider-instruction fetching order, and external money being reported by the studio. This is meaningful added disclosure beyond the structured fields, though phrased in dense domain jargon.

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 endpoint is front-loaded well, but the remaining sentences are a somewhat disjoint series of assertions (authority, policy differences, acceptance, provider instructions, pagination) that would benefit from grouping. Most statements carry information, but the ordering and density reduce scannability.

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 nested params and no output schema, the description covers behavioral context but omits what the preview actually returns and never documents the two parameters. The acceptance-vs-GET distinction helps, yet the agent still lacks enough to invoke confidently on parameter meaning and return shape.

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%, so the description carries the burden of explaining path.id, body.slot_id, and body.expected_fingerprint, but it never clarifies any of them. A reference to "the target and selection" only loosely hints at slot_id, and expected_fingerprint is entirely unexplained.

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 opens with a specific verb+resource ("Cancellation preview") and names the exact endpoint (POST /api/v2/bookings/{id}/cancellations/quotes), so the agent knows it produces a cancellation quote rather than performing a cancellation. It does not explicitly distinguish itself from siblings like podyx_get_cancellation or podyx_aftercare_amendment_preview, leaving the agent to infer the difference.

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 some implicit context ("Read/preview only", "a quote does not reserve a slot or lock a price", acceptance vs GET), but no explicit when-to-use/when-not guidance and no named alternatives among the many quote/cancellation siblings. The agent must guess whether to call this versus podyx_get_cancellation or the amendment preview.

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