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

Annotations already declare readOnlyHint=true, so safety is covered by structured data. The description adds only the underlying endpoint ('GET /teams'), which is minor context and no behavioral trait such as pagination semantics — though those are already documented in the schema for limit/offset.

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 plus an endpoint tag, with zero filler. The parenthetical definition is the highest-value content and appears immediately after the verb.

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 read-only list tool with three optional, fully documented parameters and no output schema, the definition covers what an agent needs to call it. It would be complete at 5 with one line on how to obtain a department_id or what a returned team contains.

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%, with limit, offset, and department_id each fully documented including defaults and the next_offset chaining pattern. The description's 'optionally for one department' merely restates department_id semantics, so 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?

States a specific verb and resource ('List teams') and defines the domain term precisely — teams are the rows of the schedule within a department — which is genuinely clarifying for an ambiguous noun. It does not, however, distinguish itself from nearby siblings like shiftbase_list_departments or shiftbase_list_rosters, whose names could plausibly overlap.

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?

'optionally for one department' implies that department_id narrows results and that omitting it returns all teams, which is useful implied usage. There is no explicit when-to-use guidance or routing to alternatives (e.g., list_departments first to obtain a department_id), so it stays at minimum viable.

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