Get UI/UX spec

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description usefully discloses the breadth of the payload (layout, typography, colors, interactions, responsive rules), but says nothing about output format (markdown vs structured), size, or whether it is scoped only to the homepage. With annotations carrying the behavioral baseline, this is adequate but thin.

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?

A single sentence, front-loaded with the resource and followed by a compact enumeration of what it contains. The parenthetical list is dense but earns its place; no filler or redundancy.

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 parameterless, read-only retrieval tool with no output schema, the description covers what is returned and its scope. The only gap is the return format, which an agent might want to know when planning how to consume the spec, but this is minor for a simple getter.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies no input is required, and there are no parameters whose semantics could be missing.

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 names a specific resource — the full written UI/UX specification of theknowledgehouse.org's homepage — and enumerates its contents (layout, typography, colors, interactions, responsive rules), so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from get_design_tokens or get_site_content, but the 'full specification' framing implies broader coverage than tokens alone.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to or away from siblings such as get_design_tokens (which presumably returns the token subset) or get_site_content. The scope is implied by the content description, but the agent must infer when this tool is preferable to the other design-related tools.

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