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

No annotations are supplied, so the description carries the full behavioral burden and mostly meets it: it declares the operation read-only, states the return payload, and crucially warns that the tool does not evaluate the design itself — the calling agent performs the critique. It also states the default for `rules` (design system v0.4.1). It stops short of covering error behavior or any failure modes, keeping it just under full marks.

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 the resource definition, then when-to-use, when-not-to-use, behavior, return shape, and parameter effect — a logical funnel with no filler sentences. The only minor redundancy is restating the rubric-vs-number distinction across two sentences, which could be tightened.

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?

There is no output schema, so the description correctly compensates by naming the exact return fields ({ rubric, dimensions[8], agent_prompt, output_format, verification_checklist }) and by clarifying the essential non-obvious point that the tool returns scaffolding rather than performing the critique. Nothing an agent needs in order to call this correctly 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?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantics the schema cannot express: that passing artifact/purpose/context/rules yields a pre-filled critique prompt while omitting all four returns the blank framework, clarifying the optional-parameter interaction. It stops short of describing how each field shapes the resulting prompt.

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 ('Get the Designesy Design Review framework') and enumerates its concrete contents: an 8-dimension rubric with all eight named dimensions, plus agent prompt, output format, and verification checklist. It explicitly contrasts itself with the sibling designesy_score, so the agent can distinguish rubric-delivery from numeric scoring without opening either schema.

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 an explicit when-to-use ('when you want a structured rubric to critique a design holistically') and an explicit when-not-to-use naming the alternative tool and the selecting condition ('for a deterministic numeric score, use designesy_score'). Nothing about tool choice 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.