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

With no annotations supplied, the description carries the full burden and meets it: it discloses that three internal APIs fire in parallel, that each fetches the target URL, that no browser is required, that results are cached ~24h per URL, and that an appUrl/dashboard is produced for io.modelcontextprotocol/ui hosts versus JSON for others.

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?

Front-loaded with purpose, formula, usage, execution, and return shape in a logical order with no filler prose. It runs long, and the full JSON key enumeration plus the 'One input, one output, one composite grade' restatement of the formula are slightly redundant, keeping it short of a 5.

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 tool with no output schema and no annotations, the description fully compensates, spelling out the composite formula, the agents it orchestrates, the composite and sub-result return shape, check tallies, and caching/render behavior. An agent has everything needed to call and interpret it.

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% for the single 'url' parameter, so the schema already documents it fully. The description adds only the notion that the URL is fetched by each internal API, which is marginal beyond the schema's own description.

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?

States a specific verb and resource (generate a unified design-intelligence report for a single URL) and frames it as the 'synthesis capstone' of a family. It explicitly distinguishes itself from designesy_score, designesy_drift_score, and designesy_readiness_score by naming each sibling.

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?

Gives explicit when-to-use conditions (need a single holistic assessment instead of three scans, or sharing a verdict) and an explicit 'When NOT to use' block that routes to the correct alternative for each sub-scan. Nothing is left to inference.

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