list_raspberry_pis

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'List' clearly signals a non-mutating operation, and 'available to this MCP server' adds useful scoping context. It does not explicitly state that no state changes occur, but for a simple listing operation this is a minor gap.

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, front-loaded, unambiguous sentence. Every word contributes meaning: it lists, it is scoped to named Raspberry Pis, and it is limited to those available to the server.

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 zero-parameter enumeration tool with an output schema present, the description is fully adequate. It identifies the resource and the scope without needing to explain parameters or return values, since those are handled by the schema.

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 there are no parameter semantics to document. The description correctly does not attempt to invent parameter information.

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 a specific verb ('List') and resource ('named Raspberry Pis available to this MCP server'), making the tool's purpose immediately clear. It also distinguishes itself from siblings like get_raspberry_pi_status, which targets status rather than enumeration.

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 implies when to use this tool: when you need an inventory of the Raspberry Pis available to the MCP server. However, it does not explicitly mention alternatives or exclusions, such as using get_raspberry_pi_status when you need status for a specific Pi.

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