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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: only public fields are returned, and 'for an unclaimed curated team' it exposes claim/removal links, plus the important caveat that curated teams are documented from public sources and not endorsed. It stops short of describing error behavior or whether a nonexistent slug errors versus returns empty.

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?

It is a single, front-loaded sentence with no filler, opening with the purpose before the field inventory. The long enumeration of return fields overlaps with the existing output schema, which is mild redundancy, but it remains readable and wastes little.

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 spelled out, and annotations cover the safety semantics; combined with the description's note on public-only fields and claim links, an agent has what it needs to call this correctly. The main omission is any routing guidance relative to search_teams and validate_team_profile.

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 100%, and the slug parameter already documents format and an example ('ari-collective'), so the schema carries the burden. The description adds no further meaning about the slug beyond identifying that it targets one team; baseline 3 applies.

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 scope: 'The public profile of one AgentCV team,' and enumerates the returned fields (layer, trust tier, topology, roster, evidence entries, sources), so an agent knows exactly what this retrieves. It does not explicitly contrast itself with siblings like search_teams or validate_team_profile, which is why it falls short of a 5.

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: fetch a single team by slug, as referenced indirectly through the schema note 'as search_teams returns it.' There is no explicit when-to-use statement, no guidance on when to prefer search_teams over this lookup, and no mention of what happens for an unknown slug.

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