drift_report

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

No annotations provided, but the description discloses key behaviors: read-only operation, baseline derivation, field defaults, return structure including truncation. Missing details like authorization or error handling, but sufficient for safe invocation.

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?

Front-loaded with purpose and key behavior. Structured Args and Returns. Slight redundancy in explanatory sentences but overall efficient.

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, the description fully explains the return dict and all modes of use. Covers both analysis and live inventory, baseline derivation, and default fields.

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 0%, yet the 'Args' section fully describes each parameter's purpose, behavior when omitted, and provides an example. Adds significant meaning beyond 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?

The description clearly states it reports endpoints drifted from a per-field baseline, with a specific verb 'Report' and resource 'endpoints drifted'. It answers the question 'which endpoints have drifted from the fleet?' and distinguishes from siblings by focusing on drift analysis vs other endpoint operations.

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?

Explicitly explains when to use 'endpoints' vs 'target', and that omitting 'baseline' derives fleet majority. No explicit exclusions stated, but the context is clear and actionable.

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