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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state that each action returns diagnostic guides and relevant files and that a query enables semantic search, but it omits important behavioral details such as how mode affects output, when pagination or continuation tokens are needed, and what happens when action is omitted or set to 'help'.

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 two sentences with no filler, and the core purpose and action list are front-loaded. The note about semantic search is useful, though the detailed parameter semantics were pushed to the schema rather than being summarized here.

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 7-parameter tool with a nested params object, no output schema, and no annotations, so the description must carry a lot of weight. It establishes the tool's purpose and available integrations but omits essential call semantics such as how mode and pagination interact, when continuation_token must be top-level, and what the response structure looks like. An agent would likely need to probe the tool or consult additional documentation before calling it confidently.

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%, so the description should compensate, but it only adds 'Pass query for semantic search' and names the four actions. The parameters mode, page, page_size, filter_keys, and continuation_token are not explained in the description, leaving the agent to rely on the sparse schema notes and imperfect inference.

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 identifies the tool as providing troubleshooting guides for frisian-mcp integrations and explicitly names the four supported actions: nautobot, netbox, paperless, and edx. It is clear that the tool returns diagnostic guides and relevant files for a given integration, which differentiates it from the sibling tools demo, docs, and install. A more explicit verb would make it stronger, but the resource and scope are specific.

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 does not say when to use this tool versus the sibling tools demo, docs, or install, and it gives no exclusions or alternatives. It implies the tool is for troubleshooting integrations and mentions passing a query for semantic search, but leaves the mode, pagination, and help-action behaviors to inference.

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