list_server

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no behavioral detail beyond the annotations – it simply states 'Get User Server Association' and the endpoint. It does not disclose anything about response size, pagination, or side effects, and with annotations carrying the entire safety profile, its contribution is minimal.

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 short: two lines. The first line is a purpose statement, but the second line just echoes the HTTP endpoint without adding much value beyond what the resource already implies. It is concise and front-loaded, but there is minor redundancy.

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 tool with an output schema, the description is not severely under-specified. Yet it omits any clarification of what 'User Server Association' means, and it fails to differentiate this from closely related sibling endpoints. An agent can probably call it, but will not know what kind of result to expect mentally.

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 there are no parameter semantics to explain. The description is not required to add parameter details. It receives a baseline 4 because the schema already covers everything (100% coverage).

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 does state a specific verb ('Get') and resource ('User Server Association'), so it is not a tautology. However, the resource is vague – it does not clarify what exactly an 'Association' contains, and it does not distinguish this from sibling tools like list_servers or list_server_access_tokens.

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 usage guidance is provided anywhere. There is no mention of when to use this tool, when not to use it, or how it relates to the many sibling server/list tools, leaving the agent to guess based only on the name.

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