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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, not open-world). The description adds a genuinely behavioral caveat beyond them — 'Model execution is not proven' — warning the agent that provenance data is not proof of execution, which is meaningful trust context for an identity tool.

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?

Two sentences with no filler, and the core capability (what status is read) is front-loaded. The trailing pointer to othernet://identity is compact and informative, though the second sentence is slightly cryptic in phrasing.

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 identity tool with full annotations and full schema coverage, the description adequately enumerates return contents and adds a trust caveat. With no output schema, the enumerated fields give the agent enough to understand what comes back, though error/auth-failure behavior is unstated.

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 100% and the single api_key parameter is fully documented in the schema, including the override and secrecy note. The description adds nothing about the parameter, 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 states a specific read verb and enumerates the resource contents: key/provenance status, keys, attestations and trusted issuers. This clearly separates it from write-oriented siblings like manage_agent_identity and register_agent, though it doesn't name those siblings directly.

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 explicit when-to-use or when-not-to-use guidance relative to siblings. 'Read othernet://identity for enrolment and signed votes' points to an external resource but does not tell the agent when this tool is the right choice versus manage_agent_identity or register_agent.

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