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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds non-obvious context: the call costs nothing ('Free') and requires an API key or connected account, which the annotations do not convey.

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, no filler, with the payload contents front-loaded and the actionable cross-reference last. The opening is a noun fragment rather than a full sentence, but that keeps it dense rather than vague.

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 reasonably carries the return shape by naming the fields returned and the role enum. Auth requirements and cost are covered; what it lacks is any sense of result volume or pagination, a minor gap for a simple list tool.

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?

With zero parameters there is nothing in the schema to document, so the baseline is 4. The description does add meaning about the output — that each team carries a slug and a member list with maintainer/member roles — which is more than the empty schema provides.

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 a specific resource and enumerates the returned fields (slug, name, description, members with team role), which lets an agent separate it from siblings like list_members and list_orgs without opening any schema.

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?

It gives a concrete downstream usage pattern — take a team's slug and pass it to share_file to share with the whole team — and notes the call is free. It does not explicitly state when to prefer this over list_members or list_orgs, so the routing guidance is contextual rather than exhaustive.

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