help

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

No annotations are present, so the description carries the full behavioral burden. 'List' weakly implies a read-only operation, but there is no explicit statement about safety, side effects, authentication, or rate limits. The output schema covers return values, but behavioral traits are not disclosed beyond the verb.

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 with no filler, front-loading the action and resource. It is appropriately sized for a zero-parameter tool.

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 tool is simple (zero params) and has an output schema, so return details are not needed. However, the description never explains what 'fleet surface' means or how this tool relates to sibling status and status_card tools, leaving a clear contextual gap for an agent deciding when to call it.

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 and schema coverage is 100%, so the rubric sets a baseline of 4. There are no parameters for the description to clarify, and the schema is trivially complete.

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?

State a specific verb 'List' and resource 'capabilities and fleet surface for PacketsnifferMcp', so an agent can tell it is a discovery/help tool. However, 'fleet surface' is undefined jargon and the description does not distinguish it from sibling tools like status or packetsniffer_mcp_status_card.

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 when-to-use, when-not-to-use, or alternative tool guidance is provided. The name 'help' hints at discovery, but the description itself gives no explicit context for selecting this tool over status, packetsniffer_mcp_status_card, or others.

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