AtlaSent — VQP Drift Events

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

Annotations already declare readOnlyHint=true, so the description's statement of listing snapshots adds behavioral context. It discloses the drift criteria beyond annotations, which is useful, though no extra details on auth or rate limits are given.

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 concise sentences, front-loaded with the action and resource, followed by purpose. No unnecessary words.

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 tool is a read-only listing with 4 parameters (all documented) and no output schema, the description adequately specifies what it returns and the criteria. It mentions the specific drift thresholds and usage context, which is complete for such a tool.

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 coverage is 100%, so parameters are fully documented. The description adds no additional parameter details beyond the schema; it implies filter criteria (drift/verdict change) but doesn't explain how parameters relate to these criteria.

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 it lists VQP snapshots with specific drift criteria (≥10 points or verdict change), distinguishing it from sibling tools like atlasent_vqp_generate or atlasent_vqp_audit_summary by focusing on drift events.

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?

It explicitly mentions use for compliance investigation and QA-VQP-002 §7 deviation reporting, providing clear context. It does not explicitly exclude other uses or compare to alternatives, but the purpose is well-defined.

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