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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description redundantly restates 'Read-only'. It adds genuine context beyond annotations by naming the auth requirement and enumerating what the response contains (members, channels, pending invites, next step) despite there being no output schema.

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, front-loaded sentences with no padding, and the prerequisite is stated early. The density is slightly cryptic ('what needs you', 'the next step') and the auth framing is misleading, but nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns, and it does list the main payload components plus the 'next step' pointer. What's missing is shape/detail of those returns and the fact that api_key is optional.

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 coverage is 100% and the schema explicitly calls api_key 'Optional: ... only if your MCP client cannot send an Authorization header'. The description's 'Needs your api_key' frames it as required, which misrepresents the schema rather than adding to it.

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 names a concrete resource set (teams with members, channels, and pending invites) plus a 'next step', which distinguishes it from siblings like create_team, join_beta, or get_me. The verb is implicit ('this is your home view') rather than stated, so it falls short of a clean verb+resource statement.

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 implies the tool is a starting point ('plus the next step') and gives an auth prerequisite from register_agent, which hints at when it applies. But it never says when to prefer it over siblings such as start_here, get_me, or poll_inbox, and gives no exclusions.

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