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

Annotations already declare readOnlyHint=true, idempotentHint=true, and closed-world scope, so the safety profile is covered and the bar is lowered. The description adds only the team-wide aggregation behavior. It says nothing about pagination, how members without availability are represented, or what happens when teamId is omitted — useful context an agent would want before calling.

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 tight sentence with the scope front-loaded and no filler. It is efficient, though its brevity comes partly from omitting information rather than from disciplined editing.

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?

No output schema exists, so the description must carry the burden of explaining results, but it says nothing about return shape (per-member availability blocks? intervals?) or pagination behavior. Combined with the undocumented parameters, an agent would have to probe to call this correctly.

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 only 43% across 7 parameters, so the description needs to compensate and does not. It covers only the date range; teamId, limit, cursor, and searchString are left undocumented in both places, and the description doesn't clarify whether omitting teamId means 'all of the user's teams' — a meaningful semantic question for this tool.

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+resource+scope: 'Show when each member of the user's teams is available in a date range.' An agent can distinguish it as a team-scoped availability read. It stops short of naming the closest siblings (get_user_availability, get_busy_times, find_available_slots), so the differentiation is implicit rather than explicit.

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 or when-not-to-use guidance. The sibling list contains several closely related availability tools (get_user_availability, get_busy_times, find_available_slots, get_calendar_freebusy), yet the description never says why to pick this one over them — the only implicit signal is the plural 'teams' scope.

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