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

With no annotations present, the description carries the full disclosure burden and fully delivers. It reveals several important behaviors beyond the obvious 'generate a report': it is executable and fires three internal APIs in parallel, each fetching the target URL, no browser is needed, results are cached approximately 24 hours per URL, and the output can trigger an interactive dashboard on supporting hosts. These details materially affect invocation expectations and are not inferable from the schema.

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 long, but nearly every sentence adds distinct value: composite weighting, parallel execution, cache behavior, excluded siblings, return contract, and rendering behavior are all functionally important. The use of 'When NOT to use' and 'Executable' serve as explicit structural signposts, and the riskiest information (side effects and alternatives) appears early. Slight verbosity around the internal endpoint spellings is the minor cost of that transparency.

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 single-parameter tool with no output schema, the description provides an unusually complete response contract: it enumerates every top-level field, explains the composite formula, describes sub-result structure, identifies total counts, and even notes the checks array engine tags and synthesis checks. It also covers execution semantics, caching, and rendering behavior. Nothing needed to invoke or interpret this tool is missing.

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 already describes the single 'url' parameter with 100% coverage, so the parameter semantics are fully documented there. The description adds only that the URL should be public, which is a modest but useful clarification. Per the rubric, baseline 3 applies when schema coverage is high and the description need not repeat 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 opens with a specific verb and resource: 'Generate a unified design-intelligence report for a single URL.' It clearly distinguishes itself from sibling tools by naming the three sub-scans it combines and positioning itself as the shared, synthesis capstone of the Designesy family. The explicit exclusion of the separate score/drift/readiness tools removes ambiguity.

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 explicitly states when to use this tool ('when you need a single holistic assessment instead of three separate scans') and includes a dedicated 'When NOT to use' section naming designesy_score, designesy_drift_score, and designesy_readiness_score as the alternatives. This gives an agent direct routing instructions without requiring comparison of schema or sibling names.

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