homer_search_calls_v7

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

No annotations are provided, so the description carries full burden. It mentions ms-precision and source-IP filter but does not disclose read-only nature, error handling, rate limits, or other behavioral traits. Adequate but not comprehensive.

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?

Description is well-structured with a brief introductory line followed by a clear parameter list. One sentence could be removed (e.g., the final line about the parameter list is slightly redundant with schema) but overall efficient and front-loaded.

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 7 parameters, 2 required, and an output schema present, the description covers core aspects: parameter semantics and usage context. Could elaborate on return value structure, but output schema exists to handle that. Missing a note on rate limiting or pagination, but not critical for a search 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 description coverage is 0%, but the parameter section in the description adds detailed meaning: from_ts/to_ts described as Unix ms, from_user/to_user as substring match, callid as exact, source_ip validated, limit capped at 500. This fully compensates for the schema gap.

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 'Homer 7 native search with ms-precision timestamps + source-IP filter' and explicitly distinguishes itself from sibling homer_search_calls which uses ISO strings, making the specific resource and verb 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?

Description explicitly says 'Prefer this when you are chasing a tight time window or want to filter by source IP' and references the alternative homer_search_calls, providing clear guidance on when to use this tool vs. its counterpart.

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