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

Annotations already establish readOnlyHint=true, so the description's added value is the scoping rule (no team header required) and the fact that the `_id` field is the identifier other tools consume. That is real operational context an agent would otherwise have to infer; return-format detail is partly covered by the inline payload sketch.

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?

Three compact sentences, front-loaded with the action, then the scoping caveat, then the downstream identifier semantics. The bracket payload sketch is slightly dense but short enough to earn its place as a return preview.

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 zero-parameter read with no output schema, the description covers what it returns, the shape of the response, and the required scoping context. Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the schema to document and no risk of ambiguity. The description still clarifies the ambient scoping behavior (org-wide, no x-team-id), which is the only parameter-like concern.

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 and resource ('List all teams in the Spike.sh organization') and is the only team-listing tool among siblings, so no differentiation is needed. It also sketches the returned object shape, which sharpens what 'list teams' actually yields.

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?

Explicitly frames the call as org-wide by saying it is 'NOT team-scoped (no x-team-id needed)', and explains the follow-on use of the `_id` values as `teamId` for every other tool — effectively positioning this as a bootstrap step. It stops short of naming a when-not-to-use case, but no sibling competes for this job.

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