search_procurement

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

Discloses key traits: client-side filtering on ~100 cached notices, case-insensitive substring matching, 6-hour cache. No annotations provided, so description carries full burden and does so well.

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 a note; efficient but could be better structured. No waste, but the note blends behavioral info with usage.

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 core functionality, caching, and filtering method. Missing explicit mention that date range is also client-side. Has output schema, so return values are not needed.

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 67% (missing date_from, date_to descriptions). Description adds case-insensitive matching and scope of keyword, but doesn't fully compensate for missing param descriptions.

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?

Description clearly states it searches PH government procurement from PhilGEPS open data, with specific verb and resource. It distinguishes from siblings like 'get_procurement_summary' by focusing on raw bid notice search.

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?

Implies usage for searching procurement notices, but lacks explicit when-to-use vs alternatives. No mention of when not to use, e.g., for aggregated statistics.

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