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 adds a note about configurable MCP approval requirements and business workflow approvals, which is useful context, but it is generic boilerplate and does not clarify whether this specific read operation triggers approvals or what the response behavior is.

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 purpose is front-loaded in a short first sentence. However, the second sentence about approval requirements is boilerplate and may not earn its place for a simple read-only listing operation; it could confuse rather than clarify.

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?

An output schema exists, so return values need not be explained, and annotations cover safety traits. For a one-parameter read tool the description is minimally adequate, but it lacks usage guidance and does not clarify what the returned team includes or how it relates to nearby team-member tools.

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 description coverage is 0% for the single required siteId parameter. The description implies siteId identifies 'a site,' but it adds no format, source, or constraint details beyond what the schema's UUID pattern already provides. With low schema coverage, the description should compensate more but does not.

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 verb and resource: 'Read a site's assigned team.' This clearly distinguishes it from the project-team sibling (list_project_team) because it scopes the team to a site. The only minor gap is that it does not explicitly say what 'team' contains (members, roles, etc.), but the core purpose is clear.

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 gives no guidance on when to use this tool versus alternatives such as list_project_team or list_organization_users. The second sentence discusses approval policy but does not tell the agent when this tool is appropriate or when another tool should be selected instead.

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