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

With no annotations provided, the description carries the behavioral disclosure burden. The statement that all reads and writes are real and persistent is a meaningful and important warning about side effects. It could further explain help behavior, continuation semantics, or the full mutation surface, but the core safety-relevant trait is disclosed.

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 compact, front-loads the tool's identity, packs the capability groups into a scannable list, and closes with the most important behavioral warning. Every sentence earns its place with no redundancy or filler.

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?

This is a broad tool with seven parameters, nested objects, no output schema, and no annotations. The description plus the schema's action/params/continuation_token guidance cover capability selection and basic continuation, but the description does not convey an end-to-end call pattern, expected response shape, or how to discover specific actions beyond the help hint in the schema. It is adequate but not complete.

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 low at 43%, so the description helps by enumerating the concrete resources and groups that can be used inside the params object. It does not explain the mode, page, page_size, or filter_keys parameters, but the schema already provides some structural guidance for those, making the overall parameter context adequate though incomplete.

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 identifies the tool as a live working demo of frisian-mcp and outlines the three capability groups with their subdomains. This is more than a tautology and helps distinguish the tool as an interactive demonstration surface rather than documentation or setup tooling.

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 wording implies the tool is for hands-on exploration of a live demo system, and the sibling names (docs, install, troubleshooting) make the contrast fairly clear. However, it does not explicitly state when to use this tool versus those siblings, nor does it describe exclusions or recommended first steps.

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