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

The description does not disclose side effects, authorization needs, or whether the operation is read-only. Without annotations, this omission leaves the agent guessing about the tool's behavior beyond the derivation itself.

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?

The description is a single sentence, concise and front-loaded with the main action. However, it sacrifices necessary detail for brevity, earning a 4 rather than 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?

While an output schema exists to cover return values, the description omits prerequisites, constraints, and typical usage scenarios. For a tool with no annotations and undocumented parameters, this is insufficient.

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?

With 0% schema description coverage, the description must explain parameters but does not. 'agent_id' and 'pubkey' are only named; no format, constraints, or examples are provided, leaving their meaning ambiguous.

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 clearly states the verb 'derive' and the resource 'canonical did:viridis identity', specifying the agent type (fleet R1 formula) and context (under the shared root). It distinguishes from siblings by focusing on identity derivation, though it could be more explicit about its unique role.

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?

No guidance on when to use this tool versus alternatives like viridis_agent_attestation or viridis_verify_mark. The description implies it's for deriving identities, but fails to clarify prerequisites or conditions.

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