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

readOnlyHint=true already declares the safety profile, so the description's real contribution is disclosing that each team carries its members and availability. That is useful beyond the annotations, but it says nothing about result set size, pagination behavior (despite a cursor param), or what availability means operationally.

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?

A single sentence with no filler, front-loading the verb and resource and then the payload. Nothing in it could be cut without losing information.

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, zero-required-param list tool with a fully documented schema and no output schema, this covers purpose and returned fields adequately. The only real gap is that pagination is never mentioned in prose, so an agent must read the schema to learn results are paged.

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%: both params are documented with the cursor source (meta.next) and the page-size default and max, so the schema does the heavy lifting. The description adds no parameter detail of its own, which is the expected baseline case.

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 and resource ("List Spoke teams") and disambiguates the term by equating teams with call groups, plus names the data included (members, availability). It does not explicitly contrast with siblings such as list_users or list_location_users, which an agent might otherwise consider for people-related queries.

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?

The one-line hint that members and availability are returned implies this is the browsing tool rather than a per-user lookup, but there is no explicit when-to-use, no exclusions, and no prerequisite or permission guidance. Usage is inferable rather than stated.

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