mesh_devices

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

With no annotations provided, the description carries the full burden. It discloses the required scope ('integrations:mesh:read'), implying read-only access, and mentions governance policies and ProofLink receipts. This provides useful transparency beyond the basic list action, though it does not detail potential errors, pagination, or side effects (which are unlikely for a list operation).

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 only two sentences, front-loaded with the core functionality and followed by essential access/governance context. Every sentence earns its place with no redundancy or fluff.

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 simple 0-parameter list tool with no output schema, the description covers the main aspects: what it returns, the required scope, and governance. It does not mention pagination or result limits, which might be relevant for 'all devices', but overall it is sufficiently complete for an agent to use the tool correctly.

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 has 0 parameters, and the schema coverage is trivially 100%. Per the rubric, a 0-parameter tool receives a baseline of 4. The description adds no parameter details because none exist, which 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 clearly states a specific verb and resource: 'List all devices enrolled in MeshCentral' and enumerates the returned fields (hostname, OS, connectivity, group info). This distinguishes it from sibling tools like mesh_health or trmm_agents, which focus on health or other platforms.

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 context for when to use this tool: whenever a list of MeshCentral devices is needed. While it does not explicitly name alternative tools or exclusion criteria, the purpose is specific enough that an agent can infer usage. Siblings like mesh_health are obviously different in scope.

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