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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that the response is enriched with a rating summary and recent reviews, but leaves undefined how many reviews are returned and what a missing captain yields.

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?

One sentence, front-loaded with the action and resource, with the enrichment detail trailing where it belongs. Nothing is redundant or padded.

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, the description carries the burden of describing returns, and it does so at a reasonable level (profile, rating summary, recent reviews). Minor gaps remain on review count and not-found behavior, but the tool is simple and annotations cover the safety side.

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 coverage is 0% for the single `slug` parameter, so the description must carry the meaning, and it partially does by calling it a "tenant slug." That phrasing adds context but introduces ambiguity about whether the slug identifies the captain or a tenant, which the schema does not resolve.

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?

States a specific verb and resource ("Get a captain's full profile") plus the lookup key (slug), which clearly separates it from search_captains. It stops short of naming the sibling it replaces, so the differentiation is implied rather than explicit.

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: an agent can infer this is the direct-lookup tool to use when a slug is already known, versus search_captains for discovery. The description never says when not to use it, what happens with an invalid slug, or names the alternative.

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