FlightSweeper

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

Annotations already mark the operation as read-only and non-destructive, and the description adds meaningful behavioral context: the tool is limited to the public challenge's synthetic-only boundary and must not be used for real travel transactions or private data. This materially clarifies the tool's safe operating scope beyond the 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 two sentences with no wasted words. The primary usage guidance is front-loaded, and the negative constraint is stated immediately afterward.

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 zero-parameter, read-only tool with an output schema present, the description fully covers the necessary context: it identifies what the tool describes, sets the synthetic-only boundary, and warns against misuse. No essential information is missing.

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 tool has zero parameters, so no parameter-specific detail is required. The schema coverage is effectively complete, and the description does not need to compensate for any undocumented inputs.

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 specifies a clear verb ('describe') and resource ('public FlightSweeper WebMCP challenge and its synthetic-only boundary'). It distinguishes this tool from siblings that concern contracts, safety models, and sandbox inventory by focusing on challenge capabilities and the synthetic-only scope.

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 explicitly says when to use the tool ('when an agent needs to describe the public FlightSweeper WebMCP challenge') and when not to use it ('Do not use it for real travel transactions or private data'). It does not name an alternative tool, but the exclusion criteria are clear and actionable.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'without executing or mutating a mission' aligns with that safety profile. It adds useful scope context: 'browser-local' and the exclusion of 'real travel transactions or private data,' which go 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?

Two concise sentences with no filler. The primary instruction is front-loaded ('Use this when...'), followed immediately by a clear exclusion. Every sentence carries meaningful guidance.

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 zero-parameter tool with a rich output schema and annotations covering safety, the description is sufficient. It communicates purpose, scope, and exclusions clearly. Nothing an agent needs to invoke or avoid this tool is missing.

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 tool has zero parameters and schema coverage is 100%, so there is nothing for the description to add about parameter meaning. The baseline of 4 applies because the schema fully accounts for parameters and the description correctly avoids inventing parameter details.

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 explicitly states a specific verb and resource: 'list the browser-local WebMCP tool contracts.' It also clarifies what the tool is not for ('Do not use it for real travel transactions or private data'), helping distinguish it from travel-related tools even without naming siblings directly.

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?

It gives a clear 'when to use' condition ('when an agent needs to list the browser-local WebMCP tool contracts') and an explicit 'when not to use' exclusion ('Do not use it for real travel transactions or private data'). It stops short of naming alternative tools for those excluded cases, so it misses the full alternatives guidance.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to restate safety. It adds useful context about the tool's informational scope (application-enforced model, not transactions/private data) and does not contradict any annotation. This goes slightly beyond what the structured fields alone convey.

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 two sentences, front-loaded with the primary use case and followed immediately by a necessary exclusion. There is no filler or repeated schema information, so every sentence earns its place.

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 zero-parameter, read-only tool with an output schema, the description covers what it provides and when to avoid it. An agent needs nothing else to invoke it correctly, and the output schema handles return-value details.

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 tool has zero parameters and the input schema fully documents that (100% coverage). With no parameters, the description has no parameter semantics to add, matching the baseline of 4 for parameterless tools.

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 concrete action context: describing FlightSweeper's application-enforced policy, revocation, and idempotency model. It distinguishes this from sibling tools by naming a specific domain (policy/revocation/idempotency) and adds a boundary statement ('Do not use it for real travel transactions or private data'), so an agent can tell it apart from get_challenge_capabilities and get_flight_tool_contracts.

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?

It gives an explicit positive trigger ('when an agent needs to describe...') and a clear negative constraint ('Do not use it for real travel transactions or private data'). It does not name alternative sibling tools, which prevents a 5, but the guidance is unambiguous for a simple informational tool.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is well covered. The description adds the 'bounded synthetic inventory' and 'not real/private' context, which aligns with the openWorldHint annotation. No additional behavioral details like return format are needed because an output schema exists.

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 two sentences with no filler. The usage condition is front-loaded, and the exclusion is stated immediately after. Every word adds 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 zero-parameter, read-only tool with annotations and an output schema, the description is complete. It tells the agent when to use the tool and what domain it covers, without omitting any critical invocation context.

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 tool has zero parameters, so there is no parameter burden for the description to carry. Per the baseline for zero-parameter tools, a score of 4 is appropriate since the description does not need to explain parameter semantics.

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 specific verb ('describe') and resource ('bounded synthetic inventory used by the challenge'), making the tool's purpose immediately clear. It also distinguishes the tool from real travel transactions and private data, which prevents misuse.

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?

Provides explicit guidance: 'Use this when an agent needs to describe the bounded synthetic inventory.' It also gives a clear exclusion: 'Do not use it for real travel transactions or private data.' It does not explicitly name alternative sibling tools, but the context is strong enough for an agent to decide when this tool is appropriate.

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