subscribe_shared_flights

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

It usefully discloses beyond the annotations that the call is mutating, gated behind an environment flag, and not live-validated/tested - a genuine safety signal consistent with readOnlyHint=false and destructiveHint=false. However, it never says what state changes on subscribe (new record created? subscription list entry?), nor anything about error behavior or side effects, which is the key gap for a mutation tool.

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 and write-gate are front-loaded, but the description wastes a sentence repeating itself: 'Not live-validated' and 'Mutation behavior has not been live-tested' say the same thing twice.

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?

An output schema exists so return values needn't be described, but for a non-idempotent mutation with zero parameter documentation and no explanation of effect or sibling routing, the description falls short of what an agent needs to invoke it safely.

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% across 4 parameters, and the description only notes that share_id goes under path. The generic path/query/payload envelopes and the confirm_destructive flag are left entirely unexplained, so calling this correctly requires guesswork.

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 verb and resource via the endpoint mapping (subscribe to a shared flight at /v1/flight/sharing/{share_id}/subscribe), but it mostly restates the tool name as a REST path rather than explaining what subscribing actually does for the user's account. It also fails to distinguish this from close siblings like subscribe_flight and subscribe_random_flight.

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 only guidance is a prerequisite (FLIGHTY_ALLOW_WRITES=true). There is no statement of when to choose this over subscribe_flight, subscribe_random_flight, or create_share_link, and no when-not-to-use conditions.

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