conversation_filter

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

The description lacks any behavioral details, such as whether the tool is read-only, destructive, or requires specific permissions. No annotations are provided to compensate, leaving the agent unaware of side effects or rate limits.

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?

At two words, the description is extremely concise but fails to convey necessary information. True conciseness requires completeness; this is under-specification.

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 the lack of annotations, output schema, and detailed descriptions, the tool definition is nearly useless. The agent cannot determine what the filter returns, how to interpret results, or how pagination works.

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 adds no information about parameters beyond what the schema provides. With 0% schema description coverage, the agent relies entirely on the schema property names and their types, which are insufficient for complex nested structures.

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 'Conversations Filter' is a tautology that simply restates the tool name without specifying any action or output. It does not distinguish the tool from siblings like 'conversation_list' or 'contact_filter'.

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 is provided on when to use this tool versus alternatives such as 'conversation_list' or 'contact_filter'. The tool could serve multiple unclear purposes.

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