competitive_landscape

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

With no annotations, the description carries the burden of behavioral disclosure. It enumerates output elements but does not mention data source, freshness, authentication needs, or any side effects. The description is transparent about content but not about execution behavior.

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 a single, dense sentence that front-loads the core purpose and lists specific output components. No wasted words; every element adds value. It is both concise and well-structured.

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?

Given the tool's simplicity (one parameter, no output schema), the description provides a comprehensive list of output metrics. It is almost self-contained, though it could mention data limitations or interpretative guidance for the HHI.

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 single parameter 'state' is fully described in the schema (100% coverage), and the description adds no additional semantic context beyond what the schema provides. Baseline of 3 is appropriate as the description does not need to compensate.

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 clearly specifies the tool's purpose: analyzing the competitive structure of a state's Part 135 market. It lists specific metrics (operator count, fleet-size distribution, concentration indices, HHI interpretation, leaders), distinguishing it from sibling tools like compare_operators or fleet_ranking.

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 implies usage for competitive analysis, but lacks explicit guidance on when to use this tool versus alternatives. No conditions, prerequisites, or exclusions are provided, so the agent must infer context from the tool name and sibling list.

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