list_root

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

Annotations already disclose that this is a safe, read-only, idempotent, non-destructive operation, so the main safety burden is covered. The description adds only the GET method and root path, with no additional behavioral context such as authentication expectations or response shape. There is no contradiction with the annotations.

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 extremely compact and free of filler. 'Get PMS info' states the purpose and 'GET /' specifies the invocation path, with nothing unnecessary present.

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, read-only root endpoint with an output schema present, the description is mostly complete. The main gap is that 'PMS info' does not describe what an agent should expect to find in the response, but the output schema can cover return-value 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?

The tool has zero parameters and the schema fully reflects that, so there are no parameter semantics for the description to clarify. The baseline of 4 applies.

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 an action ('Get') and a resource ('PMS info'), and the 'GET /' line makes the root endpoint explicit. However, 'PMS info' is somewhat vague and does not distinguish it from sibling tools like list_server or list_servers.

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?

There is no guidance about when to use this tool compared to the many list_* siblings, nor any mention of alternatives or exclusions. The agent must infer its role from the name alone.

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