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

The verb 'Return' indicates a retrieval operation rather than a mutation, which is a meaningful behavioral signal in the absence of annotations. However, the description does not disclose how the optional parameters affect the result, whether there are any implicit scope constraints, or what 'contracts' entails beyond the output schema.

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 short sentence with no filler. It front-loads the action and resource, making it easy to scan, though the dense list of contract types could be slightly clearer in structure.

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 tool with three optional parameters, no annotations, and a large set of related sibling tools, the description is under-specified. It does not explain parameter semantics, usage context, or how this ledger relates to the surrounding trust-profile and boundary-pack tools, even though an output schema exists.

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 mentions none of the three parameters: agent_class, identity_id, or workflow_id. With no parameter documentation in either the description or the schema, an agent cannot know how these optional fields filter or shape the returned contracts.

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 uses the specific verb 'Return' and names a clear resource: agent non-human identity, delegation, scope, and audit contracts. It is clear enough to understand the general purpose, but it does not explicitly distinguish this tool from the many similar sibling pack/recipe tools like recipes_agent_card_trust_profile or recipes_agent_handoff_boundary_pack.

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 is provided about when to use this tool versus alternatives. With roughly 60 sibling tools covering related security, trust, and contract concepts, the description gives no selection criteria or exclusion hints, so an agent must infer usage entirely from the name.

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