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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by revealing it returns only active members and by enumerating the returned fields, but says nothing about pagination, result size limits, or required auth scope for a read-only listing.

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 front-loaded sentences plus a compact endpoint reference. Every clause earns its place: purpose and returned fields first, usage hint second, API mapping last.

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?

There is no output schema, so the description usefully compensates by enumerating the returned fields (id, name, role, field tech flag, email, service areas, skills). The only gap is the absence of any note on result size or pagination behavior for accounts with many team members.

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 no parameter semantics to explain and the baseline of 4 applies. The description instead spends its space on the returned fields, which is the more useful information here.

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 the account's active team members') and enumerates the returned fields, which distinguishes it cleanly from the singular sibling workiz_get_team_member. The 'active' scope qualifier and endpoint reference (GET /team/all/) make the intent unambiguous.

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?

'Use the name to assign people to jobs or leads' hints at downstream usage, which implies this is a lookup tool for assignment flows. However, it never states when to prefer this over workiz_get_team_member or whether results should be cached, so usage is only implied rather than explicit.

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