search_insights_by_scope

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

No annotations are provided, so the description carries full burden. It states 'Handles bulk queries' which suggests performance capability, but it does not disclose any behavioral traits like side effects, authorization needs, or rate limits. For a search tool, read-only nature is implied but not explicitly stated.

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 no wasted words. The first sentence states the purpose and lists filters; the second adds a capability. It is front-loaded and clear, though slightly under-specified.

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?

The tool has a nested scope object and no output schema. The description does not mention pagination (limit/offset), required fields, or response format. The 'bulk queries' hint is vague. Given the complexity of the scope object, more detail is 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?

The description lists filters like 'product' and 'segment' that are not in the input schema, causing potential confusion. Schema has some descriptions for 'call_type' and 'sentiment', but the description adds nothing beyond field names. Since schema description coverage is 0% (or very low), the description fails to compensate.

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 tool searches insights with scoped filters, listing filter types. It specifies the action and resource, and the inclusion of 'bulk queries' hints at scale. However, it does not explicitly distinguish from sibling tools like search_by_confidence or search_recordings_metadata.

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. The only hint is 'bulk queries of 1500+ calls', implying it is for large datasets, but no explicit when-to-use or when-not-to-use information.

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