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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It explains the tool's purpose but does not disclose output format, side effects (or lack thereof), error handling, pagination, or any limitations. This is a significant gap for an agent deciding whether and how to invoke it.

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, zero fluff, and the core purpose is front-loaded. The description is efficient and earns every word, with no redundant or tangential content.

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 absence of an output schema and annotations, the description is incomplete. It does not specify what the tool returns (e.g., a timestamp, a boolean, a list), how parameters affect results, or any behavioral nuances. An agent would have to infer too much to use it 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?

The description adds no parameter-level information. The schema describes 'chat' and 'query' but leaves 'limit' unexplained (67% coverage). The description does not compensate for the missing 'limit' semantics, nor does it clarify how the parameters relate to the coverage check. Baseline is not reached because coverage is below 80% and the description offers no parameter guidance.

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 what the tool does: it reports how far back synced history reaches per chat, and it frames this as a way to answer whether a conversation exists before searching. It distinguishes itself from sibling search/list tools by focusing on coverage depth, though it could be more explicit about the exact output (e.g., a date or boolean).

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?

The description gives a clear use case: use this tool to check if you even have the conversation before searching it. This implies a pre-check step and tells the agent when to use it, but it does not explicitly name alternative tools or state when not to use it.

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