audit_flutter_accessibility

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

There are no annotations to lean on, and the description does mention that checks are performed and wrappers are generated. However, it is ambiguous whether generating the wrappers modifies the input snippet, creates new files, or only returns wrapper code in the response. For a tool without annotation support, this is a useful but incomplete view of side effects.

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, tight sentence that leads with the central audit purpose and then lists specific criteria and outcome. There is no fluff, repetition, or misplaced information.

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?

For a one-parameter tool, the description does enough to explain what gets inspected and why an outcome is generated. Still, with no output schema or annotations, the missing clarity about whether the tool edits code and what the return value looks like leaves the agent without a complete mental model of the operation.

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?

The schema covers the single parameter with a clear description ('Flutter widget code to audit'), and the tool description refers to Flutter widget trees, which closely aligns. Since schema coverage is 100%, the description only adds marginal context about the exact audit scope rather than new parameter details.

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 uses a specific verb ('Audits') with a specific resource ('Flutter widget trees') and explicitly names WCAG 2.1 AA, screen reader Semantics, and touch target size. It clearly identifies a focused accessibility audit tool and can be differentiated from audit_flutter_codebase and audit_flutter_security, though it does not explicitly say it is not those.

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 makes the use case clear: run this when auditing Flutter widget accessibility against WCAG and when wanting generated AccessibleTouchTarget wrappers. It does not explicitly mention alternatives or exclusions, but the narrow focus on accessibility makes the intended scenario reasonably obvious.

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