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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds context about the returned data (e.g., CDC inspection score, venues, editorial) but does not disclose additional behavioral aspects like error handling, rate limits, or data freshness. It does not contradict the annotations.

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 a single, front-loaded sentence that efficiently lists the data categories without fluff. It is concise and immediately communicates the scope, though it could be slightly more structured (e.g., separating core attributes from editorial details).

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?

For a read-only profile lookup with one parameter, the description adequately covers what the tool returns. It lists all major data fields, and since there is no output schema, this serves as the primary documentation. It does not mention edge cases or pagination, but those are unlikely for a single-ship 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?

The single parameter 'ship' is fully described in the schema with an example ('Carnival Breeze') and coverage is 100%. The description does not add extra meaning beyond the schema, so the baseline of 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 clearly states the resource (one ship) and enumerates the specific data categories (year built, size, guests, crew, cabin counts, ratings, etc.), making it unambiguous what this tool returns. It distinguishes itself from siblings like getShipCabins (which focuses on cabin details) and getCruiseLineProfile (which is about the cruise line).

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 implies this is for retrieving a comprehensive ship profile, but it does not explicitly state when to use this tool versus alternatives such as getShipCabins or getCruiseLineProfile. There is no mention of exclusions or conditions, leaving the agent to infer usage from the content description alone.

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