squads_get

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the 'internal' scoping qualifier and says nothing about return contents, permission requirements, or error behavior for a missing uuid.

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 short, front-loaded sentence with no filler. It is efficient, though it is terse enough that it sacrifices some useful context (which resource set, what is returned) for brevity.

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 single-parameter read with no output schema and annotations carrying the safety profile, the description is minimally viable. It omits what a squad object looks like and how a uuid is discovered, which an agent would likely need.

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?

There is a single required parameter at 0% schema description coverage, but it is self-documenting (a uuid with format: uuid) and the description confirms it is the lookup key ('by uuid'). No further meaning about format or sourcing of the uuid is added.

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 (squad) scoped to 'internal' squads, which usefully distinguishes it from the sibling external_squads_get. It does not, however, differentiate itself from squads_list or explain how a uuid is obtained.

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?

No when-to-use guidance is given. It is implied that this is the lookup path when a squad uuid is already known, but the description never says when to prefer squads_list (browse all) over this tool, nor what happens for an unknown uuid.

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