search_by_confidence

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

With no annotations, the description must disclose behavioral traits. It only states it filters insights, but does not indicate if this is a read-only operation, whether it requires authentication, or any side effects. The agent lacks information about data safety or permissions.

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?

The description is a single sentence, making it concise. However, it is under-specified; while short, it does not fully convey the tool's capabilities or constraints. It is acceptable for a simple filter but lacks depth.

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 no output schema and no annotations, the description should provide more context about return format, pagination behavior (e.g., how limit affects results), and edge cases. The tool has 3 parameters but the description does not mention how they interact. This is incomplete for an agent to invoke correctly.

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%, meaning no parameter descriptions in the input schema. The description does not add any explanation about the parameters beyond their names and schema types. For example, the 'limit' parameter's purpose is not explained. The description adds minimal value over the 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?

Description clearly states the tool filters insights by confidence score range. It uses a specific verb (filter) and resource (insights) with scope (confidence score range). Among sibling tools like search_by_validation_status and search_insights_by_scope, this description differentiates it based on confidence filtering, but does not explicitly mention why one would choose this over others.

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 explicit guidance on when to use this tool versus alternatives. The description does not provide context about prerequisites, when not to use, or mention sibling tools. For a filtering tool, it would be helpful to know typical use cases or if it should be combined with other searches.

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