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

Annotations already declare readOnlyHint, non-destructive, closed-world, so the safety profile is covered. The description adds the useful gate that it is only meaningful when vLEI is configured, but says nothing about what the response contains or how a missing/unconfigured identity is signalled.

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 short sentences with no filler, and the use condition is front-loaded. Minor awkwardness in the 'attributing calls to' phrasing keeps it from a 5.

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 zero-param read tool with no output schema, an agent still does not know what fields come back (entity name, LEI, KERI AID, attribution scope) or how to interpret the tool when vLEI is not configured. The description covers when to call it but not what to expect from the result.

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?

Zero parameters, so the baseline is 4. The description correctly implies no input is needed beyond ambient configuration, which matches the empty schema.

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 resource: the verified legal entity and agent identity that dVeracity attributes calls to. It is clear about what is retrieved, though the phrasing 'keri' vs 'vLEI' vs 'agent identity' leaves a little ambiguity about exactly which identifier is returned.

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?

It states an explicit triggering condition ('when an organisation needs to confirm which verified legal entity and agent identity...') and a precondition ('Only relevant when vLEI identity is configured'). No sibling alternative is named, but none of the listed siblings overlaps closely enough for that to matter much.

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