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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only lookup, what the ledger returns, whether results are scoped per-tenant, or how the optional filters interact - none of the context a caller needs is disclosed.

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?

It is a single short sentence with no waste, but it is under-specified rather than concise - the brevity comes from omitting essential information, not from tight writing. Nothing is front-loaded beyond a bare domain list.

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?

An output schema exists, so return-value detail is not strictly required. But for a 3-parameter tool with 0% schema coverage and no annotations, the description should at minimum explain the filters and the read-only nature of the call; neither is present, leaving the definition inadequate.

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 0% and the description adds nothing about agent_class, identity_id, or workflow_id. The word 'identity' loosely gestures at identity_id, but there is no explanation of what values these filters accept, whether they combine, or what omitting them returns.

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 has a verb ('Return') and names the domains covered (non-human identity, delegation, scope, audit contracts), which loosely distinguishes it from siblings like recipes_agent_capability_risk_register. However, 'contracts' is undefined and it never says what form the ledger takes or what 'return' produces, so an agent cannot confidently tell its exact scope from the sibling cluster.

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 statement of when to use this tool, when not to, or which sibling to prefer for adjacent questions (e.g. delegation vs. handoff boundary or capability risk). The domain nouns imply a topical fit at best; no explicit routing guidance is given.

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