list_drift_findings

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only list operation but omits details about pagination, result ordering, error handling, or whether the tool triggers side effects. The behavior is minimally described.

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 extremely concise with a single sentence that delivers the essential information: what the tool does and its primary filters. It is front-loaded and contains no redundancy.

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 3 parameters and no output schema or annotations. The description covers only two filters, leaving the 'db_path' parameter unexplained. It does not describe the return format, pagination, or any behavioral nuance, making it incomplete for an agent to use effectively.

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%, so the description must compensate. It mentions the 'status' and 'finding_type' parameters with default values but does not explain their allowed values or formats. The third parameter 'db_path' is entirely unmentioned, leaving its purpose and usage unclear.

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 verb 'list' and the resource 'stored drift findings.' It specifies two filters (status with default 'active' and type), which conveys the tool's scope and differentiates it from related tools like 'detect_drift' that create findings. However, it does not explicitly distinguish from sibling list tools like 'list_guardrail_findings.'

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 'list_guardrail_findings' or 'detect_drift.' There is no mention of prerequisites, limitations, or best practices. The agent must infer usage from the context of drift findings.

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