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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully discloses the mode-switching behavior driven by teamId, but adds nothing about invalid IDs, empty results, or team membership requirements. An output schema exists, so return format needn't be explained.

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 with no wasted words. The 'or' construction is slightly loose but still readable, and the primary list behavior comes first.

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 one-parameter read tool with full annotation coverage and an output schema, the description covers both invocation modes adequately. Minor gaps remain around the meaning of teamId values and result scoping, but nothing an agent needs 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?

With one optional parameter and 0% schema description coverage, the description carries the burden and partially compensates by revealing that teamId switches the tool from a list to a single-team read. It still gives no format, source, or lookup guidance for the ID itself.

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?

The description names a specific verb and resource ('List teams') and adds a second clear mode ('read one team's settings'), which an agent can distinguish from create_team, delete_team, rename_team, and leave_team by verb alone. It does not explicitly name any sibling, so it falls short of full differentiation.

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?

The two clauses imply when each mode applies — omit teamId to list all teams, supply teamId to read one team — but the condition is left to inference rather than stated as an explicit rule. No alternatives or exclusions are named.

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