search_search_areas

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

No annotations are provided, so the description carries the full burden. It only mentions 'fuzzy search' without revealing side effects (likely read-only), required permissions, or algorithmic details. The behavior is not clearly defined beyond the basic action.

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 sentence, which is concise but overly brief. It could incorporate additional useful context without becoming verbose, such as mentioning output or usage hints. Front-loaded structure is fine but too sparse.

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 (2 params, output schema exists) and lack of annotations, the description is incomplete. It does not explain what 'areas' are, the return format, or any behavioral constraints, leaving significant gaps for an agent to use correctly.

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 0%, so the description should explain parameters. It implies 'query' is a name for fuzzy matching and 'limit' controls result count, but it does not clarify the fuzzy algorithm, input format, or edge cases. Minimal value added beyond the 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?

The description clearly states the verb ('search'), the resource ('areas'), and the method ('fuzzy by name'). It distinguishes from sibling search tools like search_search_devices and search_search_entities by specifying the resource, making its purpose unambiguous.

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?

No guidance on when to use this tool versus alternatives. With many sibling search tools (e.g., search_deep_search, search_find_related), the description should note scenarios or prerequisites, but it does not.

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