List StreetEasy areas

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

Discloses matching behavior (case/spacing-insensitivity) and that it returns names and codes. With no annotations, this adequately conveys the read-only, non-destructive nature of the tool.

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?

Three short sentences, front-loaded with purpose. No redundant words, every sentence serves a clear function.

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 simple list tool with one optional parameter and no output schema, the description fully covers what the agent needs: purpose, parameter usage, return content, and integration with sibling 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 covers 100% of parameters, but description adds value by explaining how the search parameter works (case/spacing-insensitive matching, examples). Adds meaning beyond schema.

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?

Explicitly states 'List StreetEasy area names and their numeric codes' with a specific verb and resource. Clearly distinguishes from sibling tools like search_rentals by focusing on area codes for use in that tool.

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?

States the tool is 'for use in search_rentals' and describes optional filtering with examples. Does not explicitly exclude alternatives but clearly implies the context of retrieving area codes for rental searches.

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