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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does list the available actions and their purposes, which is useful, but it does not state whether operations are read-only, how the help flow works, how pagination or continuation tokens behave, or what side effects or auth dependencies exist.

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 a single dense, front-loaded sentence with no filler. The action list is compact and each phrase earns its place, though it could have been slightly clearer as a structured list rather than a long comma-separated run-on.

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 routing-style tool with 7 parameters, nested objects, and continuation-token mechanics, yet there is no output schema or annotation support. The description covers only action names and omits the invocation patterns needed for pagination, continuation calls, and mode behavior, leaving an agent under-equipped without deep schema inspection.

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 only 43%, and the description itself does not compensate for the gap. It mentions action names but never explains top-level parameters like mode, page, page_size, filter_keys, or continuation_token, which have non-obvious rules around continuation calls and placement inside params.

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 the entry point to frisian-mcp documentation and server guide, and enumerates seven concrete actions with one-line semantic labels. This distinguishes it from siblings like demo, install, and troubleshooting. It loses a point because 'Start here' is an orienting instruction rather than a specific verb+resource statement.

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?

'Start here' implies this tool should be used first, giving some usage context. However, there are no explicit when-to-use versus when-not-to-use statements, and the description does not clarify when to use the docs tool's demo action versus the sibling demo tool.

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