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

With no annotations provided, the description carries the full burden and does a creditable job: it discloses the public/no-authentication posture (a safe read), the version-binding scope, the non-obvious rating rule that a version is unrated until 50 resolved answers in a category, and two extra return artifacts. It does not say what happens for an unknown agent_id or describe the passport body itself, which keeps it below the top band.

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?

Three short sentences, front-loaded with the core verb and resource, followed by the access model, the rating threshold, and the auxiliary outputs. Every sentence carries distinct information and nothing is repeated from the schema.

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 at least indicate return content, and it names the passport plus the badge URL and README markdown. For a one-parameter read tool that is largely sufficient; the internal shape of the passport object and failure behaviour are left unspecified, which is the only meaningful residual gap.

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?

Only a single required agent_id parameter, and the input schema already documents it at 100% coverage, so the baseline would be 3. The description adds a small amount of meaning by framing the agent_id as the key for a public, version-bound passport, implying the identifier need not be authenticated or user-scoped.

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 verb (Fetch) and a clearly scoped resource (the public, version-bound Mizan calibration passport) keyed by agent_id, and the mention of badge URL and README markdown further pins down what this returns versus a generic agent lookup. It stops short of explicitly contrasting itself with the agent-lookup siblings, but the resource is distinctive enough that an agent can recognise it.

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 implied rather than stated: fetch this when you need the public passport artifact for an agent_id, with no auth required. There is no explicit when-not guidance and no sibling is named as an alternative, so the agent must infer the boundary with get_agent or trust_check itself.

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