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

Annotations already cover the safety profile (destructiveHint=false, openWorldHint=false), and the description usefully discloses the return payload fields, which matters because there is no output schema. It does not, however, explain or reconcile the unusual readOnlyHint=false on what reads as a pure fetch.

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 that enumerates the returned content with zero filler or repetition.

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 one-required-param read with no output schema, the description does the important work of listing what the response contains. The remaining gap is the absent routing guidance to list_squads and the unexplained readOnlyHint=false.

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 100% for the single squadId parameter, so the schema already carries the semantics. The description adds nothing about id format or sourcing beyond what the schema states, so the baseline 3 applies.

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?

Specific verb ('Get') plus resource ('one squad') and an enumeration of what comes back (invite link, players, next game, RSVPs). The word 'one' implicitly separates it from the list_squads sibling, though no sibling is named directly.

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 only implied: you call this to inspect a single squad by id. There is no explicit when-to-use/when-not, no mention of list_squads as the alternative for browsing, and no prerequisite guidance beyond the schema's 'from list_squads' note.

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