analyze_territory_disruption

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

Discloses that the tool is a paid endpoint and returns a 402 challenge in default non-settling mode, which is critical behavioral information not captured in the schema. However, does not describe behavior on successful payment or other edge cases.

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 that front-load the endpoint and then add key context about payment. No wasted words.

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?

Covers endpoint, parameters, and an important behavioral aspect (402 challenge). Lacks description of success response format, but given it's a thin wrapper, the description is reasonably complete for a simple 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 100% with descriptions for both parameters (zip and radius). Description adds that radius is in miles but does not go beyond what schema already provides. Baseline score applies.

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?

Clearly states it's a thin wrapper for a specific GET endpoint with ZIP and radius parameters, and mentions it's a paid endpoint that returns a 402 challenge. Distinguishes from sibling tools which are for different purposes.

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?

Implies usage for analyzing territory disruption with a ZIP code, mentions paid endpoint and 402 challenge, but does not provide explicit guidance on when to use vs alternatives or how to handle the payment challenge.

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