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

With no annotations, the description carries the burden. It discloses that active locations are returned by default and that addresses/contact info are included, which is useful. However, it does not mention whether authentication is required, pagination, or the meaning of 'active', leaving some room for interpretation.

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 primary purpose and include the key behavioral nuance (default active). No filler or redundant 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?

Given the simple nature of the tool (list locations) and no output schema, the description covers the basic return content (addresses, contact info) and default behavior. It could mention authentication or edge cases, but for a list tool this is reasonably complete.

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 schema provides 100% coverage for the single parameter 'include_inactive' with a clear description and default. The tool description adds no additional parameter semantics beyond what the schema already states. Baseline 3 is appropriate since schema fully documents the only parameter.

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 states a specific verb 'List' with a specific resource 'Bandago rental locations', and specifies the returned data (addresses and contact info). It distinguishes from sibling tools like 'get_rate_quote' or 'check_availability' which focus on pricing or availability.

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 listing locations and notes default behavior (active only), but does not explicitly state when to use this tool versus alternatives or any exclusions. It provides enough context for a simple list tool, but lacks explicit 'when to use' guidance.

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