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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds one piece of behavior beyond that – it returns the new squad plus its invite link – but says nothing about failure modes, name/tag uniqueness enforcement, or rate limits.

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?

One dense sentence that front-loads the purpose, embeds the endpoint, and closes with the return value. No wasted clauses.

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 mutation tool with no output schema, the description does compensate by stating what comes back (squad + invite link). However, it omits auth prerequisites and the consequences of duplicate names/tags, leaving the agent under-informed for a creation call.

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 50%: only social and requestId are documented in the schema. The description lists {name, tag, requestId} but supplies no meaning, format, or constraint for name/tag beyond what the schema's minLength/maxLength already conveys. Marginal value over the structured fields.

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 specific verb and resource ('found a Squad') and even cites the underlying endpoint, so an agent can tell it apart from memeswap_squad_apply, memeswap_squad_directory, and memeswap_squad_mine. It stops short of explicitly contrasting with those siblings, which keeps it out of the top band.

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 found a Squad' gives an implied when-to-use but names no alternatives, no prerequisites (e.g. must be logged in via memeswap_social_login), and no conditions under which not to call it. Adequate minimum, with clear gaps.

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