list_issuance_records

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

With no annotations provided, the description must carry the full behavioral burden. It does convey that the tool lists records and exposes session-level counts and trust posture, implying a read-only operation. However, it does not explicitly state the absence of side effects, or mention ordering, pagination, or potential volume, leaving some gaps in behavioral disclosure.

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 three concise sentences with no filler. The first sentence front-loads the core action and object, the second adds relevant detail about the returned data, and the third gives a practical use case. Every sentence earns its place.

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-parameter list tool with no output schema, the description covers the main aspects: what is listed, what information is shown, and a suggested use. There is slight ambiguity between 'all stored issuance records' and 'in this session', but overall the description is sufficient for an agent to understand and invoke the tool.

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?

The tool has zero parameters and the schema is empty (100% coverage by triviality), so the baseline is 4. The description adds value by explaining the kind of data returned, even though there are no parameters to describe.

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 begins with 'List all stored issuance records with their passport grades', using a specific verb and resource that clearly distinguishes the tool from sibling list tools like list_profiles and list_tasks. It also specifies the data shown (passport grades, counts, trust posture), making the purpose unmistakable.

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?

The phrase 'Useful for monitoring issuance patterns' gives a clear use case, but it does not explicitly state when not to use this tool or mention alternatives. For a simple zero-parameter listing tool, the guidance is adequate but not as strong as explicit when-to-use versus when-not-to-use.

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