diagnose_app_quality

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

No annotations provided. Description discloses return values (scores, issues, evidence locations, etc.) but does not explicitly state read-only nature or potential side effects. For a diagnostic tool, likely non-destructive, but transparency is moderate.

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?

Three sentences, no redundancy. Front-loaded with purpose and scope. Every sentence adds value.

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?

Tool has 2 optional parameters, no output schema, but description covers output structure and usage context thoroughly. No gaps for an AI agent to invoke correctly.

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 covers 100% of parameters (target, maxFiles). Description adds no new semantic meaning beyond schema; it mentions 'from code or a public URL' which aligns with target parameter. Baseline score of 3 applies.

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?

Clear verb-resource combination: 'Diagnose UI quality' for 'shadcn/Tailwind app'. Distinct from siblings like 'analyze_design' and 'run_audit' by focusing on quality diagnosis with scores and issues.

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 states when to use (before planning UI fixes, exporting registry, giving AI editor context). Lacks explicit when-not-to-use or alternatives, but context is clear enough for good guidance.

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