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 the key return shape (card plus a share link URL), but says nothing about auth/session requirements beyond the implicit 'caller own squad' and nothing about error cases.

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 front-loaded sentence with no filler; the endpoint path is dense but arguably useful for debugging. Nothing redundant, though the parenthetical URL formatting is slightly awkward.

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?

No output schema exists, and the description sensibly compensates by stating what is returned (the card plus the link). For a simple two-param read tool with rich annotations, this is nearly complete, missing only session/permission caveats.

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 only 50% (social is documented, squadId is bare), so the description carries extra weight here. It adds real semantics by constraining squadId to the caller's own squad, which tells the agent not to pass arbitrary squad IDs.

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 (get) and resource (invite/share card) scoped to the caller's own squad, plus the backing endpoint. It distinguishes itself from squad_directory/squad_mine by being explicitly about the caller's own squad, though it doesn't name a sibling by contrast.

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?

Usage is implied — 'use to get the invite card for the caller own squad' tells the agent the situation, but there is no explicit when-to-use/when-not or named alternative (e.g., vs squad_mine or squad_directory) to route between.

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