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

Annotations already declare the read-only, idempotent, non-destructive nature of the tool. The description adds useful behavioral context by stating the output fields (name, email, role) and the 'current company' scope. It does not cover pagination or empty-team behavior, but this is acceptable given the strong annotation coverage. No contradiction with annotations.

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 sentences with no filler. The first sentence states the action and scope, the second provides output details and usage cue. Information is front-loaded and every sentence earns its place.

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-only tool with comprehensive annotations and a fully described parameter, the description covers the action, output shape, and usage context. The only notable gap is the lack of distinction from the similar 'get_team_roster' sibling, which is more of a purpose-clarity issue than a completeness gap for correct invocation.

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 coverage is 100% and the parameter description is already informative ('FreedomOS company id to act within (you must be a member). Required for company-scoped tools.'). The description adds no additional meaning about the companyId parameter beyond the schema, so the 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?

The description states a specific action ('Get all team members'), scope ('for the current company'), and return shape (name, email, role). It clearly defines what the tool does. However, it does not differentiate from the similarly named sibling 'get_team_roster', leaving potential ambiguity about which tool to choose.

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 description provides explicit positive usage triggers ('Use when user asks about team, company members, who is on the team, etc.'). It does not include exclusions or mention alternatives such as 'get_team_roster' or 'get_team_pulse', so it offers clear context without when-not guidance.

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