list_applications

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

With no annotations, the description carries full burden for disclosing behavior. It states the operation is a list (implying read-only), but does not mention permissions, rate limits, or side effects. The return format is partially described but lacks details on pagination or error cases.

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 two sentences with minimal waste. The first sentence states the purpose and the second adds return format and resource context. However, it could be restructured to include parameter info without adding length.

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?

Given three parameters with no descriptions, no output schema, and no annotations, the description is incomplete. It does not explain pagination via limit/offset or the optional organization_id filter. The return format is partially described but lacking full details.

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%, meaning the input schema provides no descriptions for the three parameters: limit, offset, organization_id. The tool description adds absolutely no information about these parameters, leaving the agent to infer their meaning from names alone, which is insufficient.

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 the tool lists LoRaWAN applications on the gateway, using the specific verb 'list' and resource. It distinguishes from sibling tools like create_application, delete_application, and get_application, which have different purposes.

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 the tool is for listing all applications, but it does not explicitly say when to use it versus alternatives like get_application for a specific application or list_devices for devices. No exclusions or prerequisites are mentioned.

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