Server Info

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

No annotations are provided, so the description carries the full behavioral burden. The verb 'Report' implies a read-only, side-effect-free query, which is adequate transparency for a zero-parameter info tool. However, it does not explicitly state that it is safe to call anytime or that it reflects current server state.

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 clean sentence that front-loads the verb and the object of the query. Every word contributes; there is no filler, redundancy, or irrelevant detail.

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 query tool with an output schema present, this description is complete. The purpose is fully stated, the return value details are covered by the output schema, and there are no parameters or prerequisites to explain.

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 zero parameters and the input schema confirms an empty object with additionalProperties=false. With 0 params, the baseline is 4; the description correctly adds no param information because there is nothing to document.

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 identifies a specific verb ('Report') and a specific resource ('which Omada API spec this server is running against'). It is distinct from all siblings, which deal with operations, catalog, sites, and devices — this one is clearly a server-level metadata query, so an agent can differentiate it without inspecting schemas.

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 explicit guidance on when to use this tool versus alternatives, nor any exclusions. However, usage is implied: an agent needing to know the server's API spec version would naturally call this, and none of the siblings overlap with it. The context is clear but the description does not spell out when-not-to-use.

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