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

Annotations already declare readOnly/destructiveHint=false/openWorld, so the safety bar is low. The description adds genuinely useful context beyond that: keys are public, signing secrets are never returned, and retired keys are included — the last point materially affects how a caller should handle rotation.

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 what is returned, then a safety note, then the pinning hint. No filler; every sentence earns its place.

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 an output schema present, the description need not explain return values, and annotations carry the safety profile. It covers the public/secret distinction and retired keys, though it says nothing about key rotation cadence or caching behavior, which would help a caller relying on pinning.

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?

There are zero parameters, so per the rubric the baseline is 4. Schema coverage is 100% and there is nothing for the description to compensate for.

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 (Read) and resource (Autonet's public Ed25519 verification keys / JWKS), and adds scope (including retired verification keys). This clearly distinguishes it from siblings like agent_signed_evidence or verify_agent_domain, which consume or validate rather than expose keys.

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 'Pin issuer https://autonet.work' line hints at the verification use case, but the description never states explicitly when to call this versus alternatives such as agent_signed_evidence. Usage is implied rather than stated, and no exclusions or prerequisites are given.

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