mesh_overview

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

With no annotations, the description carries the behavioral burden and does add useful context by disclosing that it performs 'two reads, with the web-interface fallback.' It does not explicitly state read-only safety, permissions, or fallback conditions, but the operational behavior is more transparent than a bare schema.

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 sentence that front-loads the core purpose and enumerates returned fields efficiently. It is appropriately sized, though the long parenthetical listing makes it slightly harder to scan than a more structured breakdown.

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?

With no output schema and no annotations, the description fully enumerates the node and client fields an agent would receive. It gives enough return-value detail to understand the response shape without unnecessary repetition.

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 the baseline score is 4. The description correctly does not invent parameter details, and no input parameters require additional semantic explanation.

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 resource and contents: a mesh overview with detailed per-node and per-client fields. It is specific about what data is returned, but it does not explicitly differentiate itself from sibling tools such as get_router_data or router_snapshot.

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 phrase 'at a glance' implies a summary use case, but the description never states when to prefer this tool over alternatives like get_router_data or router_snapshot. Usage is only implied, not explicitly guided.

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