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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuine context beyond that: the feature-flag prerequisite and the concrete failure mode (HTTP 403), plus a hint at the response payload shape. Pagination or result-size behavior is not disclosed, keeping it short of a 5.

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?

Three short sentences, front-loaded with what is returned, then the prerequisite and the failure mode. The trailing 'GET /teams' endpoint notation is mildly redundant with the tool name but is compact and harmless.

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 carries the burden of describing returns — it does so at a summary level (teams, members, managers). Combined with the disclosed prerequisite and error behavior, an agent has enough to call it correctly; only pagination/vollume details are absent.

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, which is the baseline-4 case. Nothing in the description is needed to explain inputs, and it correctly implies an unfiltered full listing.

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 the resource and its payload concretely: sales teams, their members, and who manages each — an agent immediately knows this is the 'list teams' read. It doesn't name a sibling or contrast with nocrm_list_users, but the resource is distinct enough from the other list_* tools that confusion is unlikely.

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?

Usage is only implied: the tool lists teams, so use it when team data is needed. The one real guideline given is the account prerequisite (Teams feature enabled, otherwise HTTP 403), which is a useful pre-condition but not a when-to-use-vs-alternative rule. No mention of when to prefer nocrm_list_users instead.

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