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

Despite no annotations, the description explicitly states 'Read-only' and 'from operator command-center cache' and an availability constraint, disclosing key behavioral traits such as non-mutation, data source (cache), and local-only availability. This exceeds minimal transparency for a no-annotation tool.

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 sentence, front-loaded with '[Local ops]', and efficiently packs context, read-only nature, source, and availability into a concise phrase. Every word serves a purpose with no redundancy.

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?

The description provides source, availability, and read-only nature, and the schema documents the limit parameter. However, with no output schema, it does not explicitly describe the return format or clarify what 'mesh' and 'node' mean, leaving some gaps for a complete invocation picture.

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 only parameter 'limit' is fully documented in the schema with 'Max nodes to return (default all)', and the tool description adds no additional meaning about the parameter. With schema description coverage at 100%, the baseline of 3 is appropriate.

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 states 'Read-only mesh snapshot from operator command-center cache', clearly identifying the resource and read-only nature, and the tool name 'list_mesh_snapshot' implies listing. However, 'mesh' is ambiguous and the description does not explicitly differentiate from other list_* sibling tools.

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 provides clear usage context with '[Local ops]' and an availability constraint '(available:false off-host)', which effectively indicates when not to use (off-host). It does not mention alternatives or specific when-to-use scenarios beyond local ops.

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