set_flight_mine

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

The description adds one fact beyond the annotations: the write-gate precondition ("Requires writes enabled"), which is meaningful context for a mutation tool. Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered; the description does not explain failure behavior (e.g., what happens for an untracked flight_id) or the tension between the boolean set-state semantics and idempotentHint=false.

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 with the action front-loaded and the precondition trailing; no filler. It is efficient, though the brevity edges toward under-specification rather than maximal conciseness.

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?

With only two simple non-nested parameters and an output schema already present, the tool is low-complexity and the description need not explain return values. It is nonetheless thin for a mutation operation: it omits what "tracked" means, error conditions, and how toggling interacts with existing flight state.

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%, so both parameters are bare titles ("Is Mine", "Flight Id") with no documentation. The description's phrase "mark/unmark a tracked flight" only loosely implies that is_mine=true marks and false unmarks, and it says nothing about the expected format or provenance of flight_id. The description therefore fails to compensate for the coverage 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?

States a specific verb pair (mark/unmark) and a specific resource attribute (My Flight status on a tracked flight), which is distinguishable from siblings like set_flight_archived or set_flight_note. It stops short of naming those siblings explicitly, so an agent must infer the distinction from the attribute name alone.

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?

"Requires writes enabled" gives a concrete precondition for calling the tool, which is real guidance. However, there is no explicit statement of when to prefer this over set_flight_archived or what qualifies as a "tracked" flight, so the agent must infer the rest.

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