subscribe_random_flight

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by stating the side effect explicitly ('changes tracked flights') and flagging the prerequisite that writes must be enabled, which annotations cannot express.

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?

Two short sentences, no redundancy, with the effect and the precondition front-loaded. Nothing could be cut without losing information.

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 need not be described, and the mutation effect plus write prerequisite are covered. However, the description says nothing about how the 'random' flight is selected (scope, duplicate behavior) or what is_passenger does, leaving meaningful gaps for an open-world mutation 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 coverage is 0% and the single parameter is_passenger is never mentioned in the description, so an agent gets no explanation of what marking a flight as a passenger versus non-passenger means. The only parameter's semantics are left entirely to a bare boolean with a default.

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?

States a specific verb and resource ('Add a random flight to the account'), and the word 'random' distinguishes it from the sibling subscribe_flight. It does not explicitly name subscribe_flight as the deterministic counterpart, so the differentiation is implicit rather than stated.

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 write-mode prerequisite ('writes must be enabled') is stated, which is useful, but there is no guidance on when to use this versus subscribe_flight or subscribe_shared_flights, and no exclusions or when-not conditions. Usage is only implied by the tool name and purpose.

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