list_identity

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the exact HTTP endpoint and method, which is mildly useful, but it does not disclose additional behavioral traits such as authentication needs, rate limits, or response characteristics beyond what annotations and output schema already provide.

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 very short and front-loaded, with 'Get PMS identity' as the first line. The second line 'GET /identity' is somewhat redundant with the first line, but it is brief and provides the concrete endpoint, so the extra cost is minimal. No filler or unnecessary detail is 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 parameterless, read-only identity lookup with rich annotations and an output schema, the description is essentially sufficient. It could clarify what 'PMS identity' includes, but the output schema covers the return structure, and annotations cover the operational profile. No critical information for invoking the tool correctly is missing.

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, so parameter documentation is unnecessary. The description does not need to compensate for any schema gaps, and the schema coverage is trivially 100%. The baseline of 4 for a parameterless tool is appropriate.

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 action and resource: 'Get PMS identity.' It clearly indicates this tool retrieves identity information, and the endpoint 'GET /identity' reinforces the target. It does not explicitly contrast with sibling tools like list_server or list_accounts, but the resource is distinct enough to avoid serious ambiguity.

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 guidance is provided about when to use this tool versus alternatives such as list_server, list_servers, list_user, or list_accounts. The description implies use for identity retrieval but gives no context, exclusions, or selection criteria. With a large sibling set, this is a noticeable gap.

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