search_enterprise_policy

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

No annotations are provided, so the description carries the full behavioral burden. 'Hybrid retrieval' hints at a combined semantic/keyword search but gives no detail on ranking, result limits, coverage, or permissions. For a search tool with zero annotation coverage, this is thin.

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?

A single short, front-loaded sentence with no wasted words. Its brevity borders on under-specification, but the structure itself is clean and 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?

Although an output schema exists and return values need not be explained, the definition omits query semantics and any routing guidance against the near-identical search_enterprise_docs sibling. For a search tool with no annotations, these omissions leave the agent under-informed.

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?

The single required parameter 'query' has 0% schema description coverage and the description says nothing about its expected form, syntax, or natural-language behavior. With the schema providing no semantics, the description should compensate and does not.

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 states a verb and resource ('Search enterprise policies'), so the basic operation is clear. However, it does not differentiate this tool from the very similar sibling search_enterprise_docs, and 'hybrid retrieval' describes mechanism rather than scope. It largely restates the tool name with a mechanism tag.

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?

There is no statement of when to use this tool versus the close sibling search_enterprise_docs, nor any exclusion or prerequisite. The agent must infer the distinction from the names alone.

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