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

The readOnlyHint already covers the safety profile, but the description adds useful behavioral context: it says pending invitations require the remote person's browser review and that permission state is included in results. It does not discuss auth or rate limits, but those are minor for a read-only list.

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?

Three short sentences with the purpose front-loaded, followed by pagination and a pending-invitation behavioral note. Nothing is redundant or padded.

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 simple read-only list with full parameter schema coverage and an output schema, the description covers purpose, pagination, and pending invitations adequately. It could better distinguish this from the local connections list, but the federation prefix and title make the scope reasonably clear.

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%, so the schema already documents both parameters fully. The description only adds 'Use next_before_id for another page,' which does not add syntax beyond the schema and slightly mismatches the actual parameter name 'before_id'.

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?

States a specific verb (list) and resource (federated connections) plus their permission state, and the title clarifies 'on other ppl servers.' It does not explicitly distinguish from the sibling 'connections.list', but the 'federated' qualifier provides reasonable separation.

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 when-to-use guidance or alternatives are given. The pagination note is parameter mechanics, not tool-selection guidance, and nothing tells the agent when to choose this over 'connections.list' or 'federation.connections.invite'.

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