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

Annotations already carry readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds a genuinely useful behavioral trait beyond the annotations: the owner-only authorization constraint, which an agent needs to know before calling. There is no contradiction between the 'List' verb and the readOnlyHint.

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?

One short sentence with the verb and resource front-loaded, and the ownership constraint efficiently parenthesized. Every word earns its place; there is no filler or repetition of what the annotations already state.

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 single-parameter, read-only list tool whose annotations cover the safety profile, the description covers purpose, scope, and authorization — the essentials. Minor gaps remain: there is no output schema, so the return shape of the share links is unstated, and behavior when a non-owner calls the tool is not described. These are acceptable omissions for such a simple tool.

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 100% (tripId is already documented as 'Trip ID'), so the baseline is 3. The description's 'for a trip' phrase loosely reinforces that tripId identifies the trip whose share links are listed, but it adds no format, validation, or additional semantic detail beyond what the schema provides.

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 'List all share links for a trip (owner only)' names a specific verb (List), a specific resource (share links), and a scope (for a trip), which clearly distinguishes it from siblings like trip_share_create, trip_share_revoke, and trip_collaborators_list. The 'owner only' qualifier further sharpens the purpose. An agent can tell exactly what this tool does without opening the schema.

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 gives useful context ('owner only') which implies a prerequisite, and the sibling naming convention suggests this is the read counterpart to trip_share_create/trip_share_revoke. However, it never explicitly states when to use this tool versus alternatives or when not to use it. Usage must be inferred rather than spelled out.

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