list_rules

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

No annotations are provided, so the description carries full burden. It describes filtering capabilities but lacks behavioral details such as whether this is a read-only operation (implied by 'List'), potential rate limits, authentication requirements, pagination behavior, or output format. For a tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

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, efficient sentence that front-loads the core purpose ('List all Magento coding standard rules') and then lists filtering options. It avoids redundancy, though it could be slightly more structured (e.g., separating core action from options).

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 annotations, no output schema, and 3 parameters with full schema coverage, the description is adequate for a simple listing tool but incomplete. It covers the purpose and filters but lacks details on behavioral traits (e.g., read-only nature, response format) that would help an agent use it correctly in context.

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 100%, meaning the input schema fully documents the three parameters (category, minSeverity, searchTerm) with descriptions. The description adds minimal value by listing the same filters without additional syntax or format details beyond what the schema provides, meeting the baseline for high schema coverage.

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 'all Magento coding standard rules', making the purpose specific and unambiguous. It distinguishes from siblings like 'check_security' (which likely checks code) or 'explain_rule' (which explains a specific rule) by focusing on listing rules with filtering options.

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?

The description implies usage for listing rules with optional filters (category, severity, search), but provides no explicit guidance on when to use this tool versus alternatives like 'get_rules_summary' (which might provide aggregated data) or 'check_security' (which might involve rule application). It lacks clear when-not-to-use statements or named alternatives.

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