list_deviances_by_directory

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

No annotations exist, and the description does not disclose behavioral traits. It fails to mention pagination (page, perPage, lastIdentifierSeen parameters), result size limits, or whether the list is complete. The agent gets no sense of side effects or expectations.

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 a single, concise sentence, but it is too terse given the tool's complexity (7 parameters, pagination, filtering). Important information is omitted, making it under-informative despite brevity.

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 description is incomplete for a list tool with multiple query parameters, no output schema, and no annotations. It lacks essentials like pagination behavior, filtering options, and the meaning of 'all deviances' (are there limits?). Sibling tools suggest different scoping, but no context is given.

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% but parameter descriptions are minimal (e.g., 'Query parameter: page'). The description adds no additional meaning to the parameters beyond what the schema provides. The required parameters (infrastructureId, directoryId) are implied but not explained.

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 'Get all deviances for a directory' clearly states the action (get/retrieve) and resource (deviances) scoped to a directory, differentiating it from similar tools like get_deviance_by_directory (single deviance). However, it does not explicitly distinguish it from other list tools.

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 on when to use this tool versus alternatives such as list_deviances_by_checker or list_deviances_by_directory_and_checker. No prerequisites or context about filtering, pagination, or result limits provided.

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