get_graph_insights

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

There are no exploreIntents, so the description carries the full burden, but it only lists what it computes. It does not state whether this is a safe read-only analysis, whether it can be expensive on large wikis, or what form the results take. The get_ prefix implies a read, but nothing in the description confirms it.

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 that front-loads the verb and resource and immediately enumerates the outputs. It earns its place with zero filler, but the terse style also means useful behavioral and usage context is absent.

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 zero-parameter tool with no output schema, the description is close to sufficient from an invocation standpoint. However, the lack of any note distinguishing it from find_orphans and run_wiki_health, plus no hint about the shape or volume of returned insights, leaves meaningful ambiguity.

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 there is nothing for the description to explain. Schema coverage is 100% by construction, and the description correctly communicates that this is an analysis over the whole wiki, which is the only relevant semantic content.

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 uses a specific verb-plus-resource structure ('Compute graph insights for the wiki') and lists concrete outputs: top hubs, orphans, broken links, fragmented tag clusters. It makes the tool's goal clear, though it does not explicitly distinguish it from overlapping siblings like find_orphans or run_wiki_health.

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?

No guidance is given on when to use this tool versus alternatives. The wiki contains find_orphans, run_wiki_health, and suggest_links that could overlap, but the description neither names them nor explains what makes get_graph_insights the right choice.

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