overview

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

The [READ] marker is consistent with readOnlyHint=true, so no contradiction, but it is redundant with the annotation. The description adds that this is a one-shot aggregate (network + device rollup), which is useful scope context, yet it says nothing about auth requirements, pagination/rate limits, or result shape. With annotations covering the safety profile, a 3 is appropriate.

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?

Front-loaded with the operation and its scope, then the triage guidance, then a compact Args block. Efficient overall, with only minor redundancy in the [READ] prefix duplicating readOnlyHint.

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?

No output schema exists, so the description should ideally sketch return values; it hints at content ('networks + device status/product rollup') but not structure or aggregation level. Combined with the covered annotations and documented params, it is largely sufficient for triage-oriented calling.

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 0%, so the description must carry the load, and it does document both parameters: org_id ('omit to use the target's default org') and target ('Target name from config; omit for the default'). The defaults-sourced behavior for 'target' is genuinely beyond the schema, though what constitutes a valid target is only loosely defined.

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?

States a specific verb+resource scope: a one-shot fleet health rollup combining 'networks + device status/product rollup'. This clearly distinguishes it from point tools like device_status, org_device_statuses, and network_traffic, which cover narrower slices.

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?

Explicitly says 'Call this first to triage a Meraki organization before drilling into a specific network or device,' giving a clear ordering and context. It stops short of naming the specific alternative tools (e.g. device_status, network_get) or stating when not to use it, so it lands at 4 rather than 5.

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