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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the response contains invite links and a nextCursor, which tells the agent this is a paginated listing.

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 front-loaded sentence with no filler; the action, filter, endpoint, and return shape all fit compactly. Slightly dense but every clause carries 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 4-parameter paginated list tool with no output schema, the description covers the core action, one filter, and the paging signal. It omits what limit controls, how to request the next page, and auth expectations for the session cookie, so it is only minimally complete.

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 only 25% (only 'social' is documented). The description partially compensates by implying search semantics ('by name or tag') and cursor pagination (nextCursor), but limit, cursor bounds, and defaults remain undocumented in both places.

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 (browse/search) plus resource (squads) and scope (by name or tag), and even names the underlying endpoint. It is clearly distinguishable from siblings like memeswap_squad_mine (own squads) or memeswap_squad_create.

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?

"Use to browse or search squads" gives an implied usage context, but there is no explicit when-not guidance and no named alternative (e.g., memeswap_squad_mine for the caller's own squads). Adequate but leaves routing to inference.

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