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

Annotations already establish safety as a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavioral context by explaining which facts are derived versus stored and that checklist items are marked met or missing, though it does not discuss permissions or error behavior.

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?

The description is front-loaded with the core resource and then details returned fields, but it is a dense run-on sentence that could be more scannable. Every clause appears to add useful information, so it is efficient if not optimally structured.

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?

With no output schema and zero parameters, the description carries the burden of explaining return values, and it does so thoroughly by naming each field group and the checklist statuses. Annotations cover the safety profile, so nothing essential is missing 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?

The tool takes zero parameters and schema coverage is 100%, so parameter semantics are not a concern. The description appropriately avoids redundant parameter information.

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 clearly identifies the resource as the signed-in person's teams and enumerates the returned contents, including derived facts and checklist states. It is specific enough to distinguish a read-my-teams operation from generic team listings, but it never explicitly contrasts itself with sibling preview_teams or other team-related tools.

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?

There is no explicit guidance on when to use this tool versus alternatives such as preview_teams or read_profile. Usage is only implied by the description of returned data, leaving the agent to infer the appropriate context.

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