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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the meaningful constraint that key provisioning happens on the rooms page, not in chat, but says nothing about result volume, pagination behavior, or whether keys are returned for the whole organization vs. the caller's rooms.

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?

Two short sentences plus a compact path/group tag, with the resource definition front-loaded. The text largely restates the title, but there is little waste overall.

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 read-only listing of four scalar fields with a fully documented optional query object and no output schema, the description is sufficient: resource scope, returned fields, and a key behavioral constraint are all present. Only pagination/volume expectations are unaddressed.

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 100% for the single optional `query` object, so the schema carries the parameter burden and baseline 3 applies. The description adds no meaning about limit/cursor usage beyond what the schema already states.

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 resource — the organization's AI model keys for rooms — and enumerates the returned fields (id, provider, label, last4), plus the underlying GET /rooms/keys path. The verb is left implicit (read/list is inferred from the path and the readOnly annotation), but an agent can still tell this apart from sibling room tools such as complete_rooms_channels or complete_rooms_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?

It provides one useful exclusion — a new key is added on the rooms page, never through the chat — which tells the agent not to attempt key creation here. However, there is no explicit statement of when to call this tool versus alternatives, and the guidance is implied rather than framed as usage rules.

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