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 adds useful context by noting it needs no connection and is limited to public-record data, but says nothing about behavior for an unknown or malformed publicId. With an output schema present, the omission of return details is acceptable.

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 resource and scope, followed by the keying parameter and the no-auth condition. Nothing is redundant, though the phrase 'credential image links' is slightly opaque for what it actually returns.

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 single-parameter read tool with annotations and an output schema, most structural burden is already handled. The remaining gap is behavioral: no guidance on whether a missing or invalid publicId errors or returns empty, which matters for a public lookup keyed on an opaque identifier.

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%, so the description must carry the burden of explaining publicId, and it only restates that lookup is 'by publicId.' It does not explain what a publicId is, where it comes from, or its expected format, leaving the sole required parameter underspecified in both places.

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 pair: it retrieves the public profile metadata and credential image links of exactly one fan, keyed by publicId. The qualifier 'on the public record' implicitly distinguishes it from get_my_record, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

'Needs no connection' tells the agent it works without authentication, but the description never says when to choose this tool over get_my_record, get_leaderboard, or share_card. There are no exclusions and no stated prerequisites beyond that single clause.

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