storage_facility_details

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

With no annotations, the description fully relies on itself. It transparently lists the data returned (unit sizes, prices, amenities, hours, reviews), implying read-only and safe operation. However, it does not mention error behavior or rate limits.

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, well-structured sentence that immediately identifies the tool's purpose and lists key outputs. 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?

Given the low complexity (one parameter, no output schema), the description is complete enough. It clearly explains what the tool does and what data it returns, satisfying the agent's needs for this simple retrieval operation.

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 input schema has 100% description coverage for its single parameter 'url', which is described as 'SelfStorage.com facility URL'. The description adds no additional meaning beyond the schema definition. Baseline 3 is appropriate.

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 the action ('Get full details'), the resource ('a specific self-storage facility'), and lists included data (unit sizes, prices, amenities, hours, reviews). It distinguishes itself from sibling tools like 'search_storage' and other detail tools.

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 when details of a specific facility are needed, but does not explicitly mention prerequisites (e.g., obtaining a URL from 'search_storage') or when alternatives should be used. No exclusion criteria or alternatives are provided.

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