get_internal_squad

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 the underlying endpoint (GET /api/internal-squads/:uuid), but says nothing about return shape, 404/error behavior, or auth requirements, so it adds only modest context.

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?

Two short lines, front-loaded with the action and resource; no filler. The endpoint tag is compact and useful rather than padding.

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 single-parameter read whose annotations already cover safety, this is nearly adequate, but with no output schema it omits what a squad object contains and what happens when the uuid is unknown, leaving an agent to discover the return contract by calling it.

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 1 parameter at 0% schema description coverage; the schema does enforce uuid format and a strict pattern, so typing is handled structurally. The description only restates 'by uuid' and adds no meaning about which squad identifier is expected or where it comes from.

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 (internal squad) with the identifier qualifier 'by uuid'. It contrasts implicitly with siblings like get_internal_squads (list) and get_external_squad_by_uuid (external variant), though it never names them explicitly.

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?

Only 'by uuid' implies when this applies; there is no statement of when to use this versus get_internal_squads or get_external_squad_by_uuid, and no prerequisites or exclusions are given.

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