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

Annotations already indicate readOnlyHint=false and destructiveHint=true, so the destructive nature is covered. The description adds an authentication/authorization requirement ('owner only'), which is behavioral context beyond the structured annotations.

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 a single compact sentence that conveys the operation, the resource, and the access restriction without any redundant phrasing. Every word contributes value.

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 single-parameter destructive operation with annotations covering the destructive hint and the description covering the owner-only condition, the essential context is present. There is no output schema, but none is needed to understand the basic call. More detail about side effects or permanence could slightly improve completeness, but the annotations already mitigate that gap.

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 input schema already provides 100% coverage with a clear description for the single parameter, shareLinkId. The tool description does not add any additional parameter-level meaning, matching the baseline for schema-heavy coverage.

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 clear action ('Revoke/delete') on a specific resource ('a share link') and adds a critical scope condition ('owner only'). This makes its purpose immediately distinguishable from sibling tools like trip_share_create and trip_share_list.

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 'owner only' condition gives useful context about who may invoke this tool. However, the description does not explicitly state when to prefer this tool over alternatives such as trip_share_create or trip_share_list, leaving the decision implied rather than stated.

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