analyze_results

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

Describes core behavior (AI analysis, insights, patterns, summaries) but no annotations present. Fails to disclose specifics about AI processing, side effects, or constraints – adequate but not rich.

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 sentences with zero waste. First sentence defines action, second provides usage context and scope. Highly efficient.

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 purpose, usage, and data types. Lacks details about output format or limitations. Given no output schema, some expectation for output description exists, but the tool is simple enough that 'insights, patterns, and summaries' may suffice.

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?

Only one parameter 'question' with schema description. Description adds helpful examples ('which areas are most dense?', 'what is the price trend?'), enhancing understanding 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?

Clearly states it analyzes last search results using AI, providing insights, patterns, and summaries. Differentiates from sibling tools that are search/export focused.

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?

Explicitly recommends use after search returns results and lists compatible data types (land use, HDB resale, amenity). Lacks explicit 'when not to use' or alternative tool references.

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