list_deviances_by_directory_and_checker

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

No annotations provided, so description must carry full burden. It notes that profileId is a 'lens, not a container', which is useful, but it does not disclose pagination behavior despite page/perPage parameters, nor any other behavioral traits like result 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?

Two sentences, no wasted words, information is front-loaded and to the point.

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?

Covers the tool's purpose, required parameters, and a key nuance about profileId. However, it omits mention of pagination (page/perPage) and the return type, relying on the schema but not fully informing an agent about expected outputs.

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%, baseline 3. The description adds meaningful context for profileId (lens vs container) beyond the schema's basic 'Path parameter: profileId', but other parameters lack additional semantics.

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 'Get all deviances related to a single directory and checker', distinguishing it from sibling tools like list_deviances_by_directory and list_deviances_by_checker that filter by only one dimension.

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 instructs not to assume profile 1 and to call get_preferred_profile or get_preferences first if the user hasn't specified a profile. Differentiates when to use this tool based on both directory and checker being needed.

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