trmnl_cancel_connection_attempt

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

The annotations already declare this as destructive, idempotent, open-world, and not read-only. The description adds useful context beyond that: the attempt must be owned, it changes remote state, and it should be run only within user-authorized scope. It does not detail the exact post-cancel state, but the annotation profile lowers that burden.

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 definition is short and front-loaded with the core action and resource. The endpoint and authorization notes are useful, though the phrase 'Changes remote state or starts work' is somewhat generic. It is efficient overall.

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 simple destructive cancellation tool with rich annotations and no output schema, the description covers the relevant action, ownership precondition, remote-state impact, and authorization scope. It could mention the confirm/get alternatives more explicitly, but nothing critical is missing for 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 covers the profile parameter and identifies the nested path.id as a UUID, while the description supplies the endpoint context showing that id refers to the connection attempt. It does not add much beyond the schema, and it does not explain the profile parameter. At 50% schema description coverage, this is adequate but not compensating heavily for the gap.

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 gives a specific verb and resource: cancel a connection attempt, limited to owned pending or exchanging attempts. The DELETE endpoint reinforces that it is an attempt-level cancellation. It is clear, though it does not explicitly name the nearby confirm/get siblings as alternatives.

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?

It implies when this tool applies by saying the attempt must be owned and pending or exchanging. However, it gives no explicit when-not-to-use guidance and does not mention confirm_connection_attempt or get_connection_attempt as alternatives. The authorization sentence is a constraint, not routing guidance.

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