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

No annotations are provided, so the description carries the full burden, yet it only enumerates return contents. It says nothing about read-only nature, auth/permission requirements, privacy implications (despite a set_privacy sibling), or behavior when verification is incomplete.

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 compact and front-loads the headline (portable verified passport with three scores), but the tail is a dense comma-run of contents that reads like a data dump rather than structured guidance. No wasted prose, but little organization.

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 must describe the return payload, and it does list the main components. However it omits the relationship to get_passport, privacy/permission context, and any failure modes, leaving an agent short of what it needs to choose and invoke correctly.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 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 conveys what is returned (three 0-100 scores with level/breakdown, certs, roles, per-task matrix) but is a noun-phrase fragment rather than a stated verb+resource, so the action is only implied by the name. It does not distinguish itself from the sibling get_passport, which sounds like the same resource.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. Given siblings like get_passport and share_passport, an agent cannot tell from the description which one to call for which need.

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