list_devices

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable context: it explicitly states 'Credentials are never returned,' which is a meaningful behavioral disclosure beyond the annotations. It also indicates the returned data is device titles, providing more transparency about output.

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 concise (three sentences) and front-loaded with the primary purpose. The second sentence elaborates usage, and the third delivers an important safety note. Every sentence earns its place without redundancy or padding.

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 discovery tool, this description is complete: it states what is listed (devices and titles), how the output is used by other tools (as `device` arguments), and the visibility of credentials. The presence of an output schema covers return-value details, so the description fills the semantic gaps.

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 no parameters, so schema coverage is 100% and baseline is 4. The description adds context about the `device` argument used by other tools and mirrors the device-title concept, which indirectly informs the parameter semantics for the overall API even though this specific tool has zero params.

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+resource: 'Lists the MikroTik devices this server manages.' It clarifies the purpose and adds that it reveals device titles, which distinguishes it from the numerous sibling tools that operate on specific devices.

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?

Explicit guidance is provided: 'Every other tool takes an optional `device` argument that must be one of the titles returned here.' It explains when to use this tool (discovery) and how it relates to all other tools, including the automatic device selection when only one is configured.

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