aesthetics-wiki-mcp

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

Annotations already declare readOnlyHint=true, idempotentHint=false, and openWorldHint=true, covering safety and data behavior. The description adds value by specifying the source ('wiki') and the random nature of retrieval, which isn't captured in annotations. It doesn't contradict annotations, as 'Get' aligns with read-only, and it provides useful context beyond structured data.

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 front-loaded with the core purpose, followed by structured sections for Args and Returns. Every sentence earns its place: the opening line sets context, and the bullet points efficiently document parameters and output without redundancy. It's appropriately sized for the tool's complexity.

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?

Given the tool's low complexity (1 parameter, no nested objects), the description is complete. It explains the purpose, parameter semantics, and return format. With annotations covering behavioral traits and an output schema implied by the Returns section, no additional details are needed for effective use.

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 0%, so the description carries the burden. It clearly explains the 'count' parameter: 'Number of random pages (1-10). Default 1.', adding meaning beyond the schema's basic type and title. This compensates well for the low coverage, though it doesn't detail other potential parameters if they existed.

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 clearly states the tool's purpose: 'Get one or more random aesthetics from the wiki — great for inspiration.' This specifies the verb ('Get'), resource ('aesthetics'), and source ('wiki'), with a helpful usage context ('inspiration'). However, it doesn't explicitly differentiate from sibling tools like 'get_aesthetic' or 'search_aesthetic', which likely retrieve specific rather than random aesthetics.

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 implies usage for inspiration and randomness, but doesn't explicitly state when to use this tool versus alternatives like 'get_aesthetic' or 'search_aesthetic'. It provides some context ('great for inspiration') but lacks clear guidance on exclusions or direct comparisons to sibling tools.

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