Get certificate resources

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

The readOnlyHint annotation already establishes the operation is read-only. The description adds meaningful behavioral context beyond the annotation: the tool rejects Certificate-type entries and cannot enumerate all certificates. It does not detail return format or pagination, but this is adequate given the annotation coverage.

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 fluff. The main purpose is front-loaded, followed by the prerequisite and the key limitation, so an agent can quickly extract the essential information.

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?

The description is sufficient for safe invocation: it names the required input source, explains the type restriction, and states the tool's listing limitation. It does not describe the output shape or the behavior of the OData-style query parameters, but the read-only annotation and clear purpose lower the burden.

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 description adds important meaning for hex_alias, clarifying that it must come from a Key Pair entry even though the schema does not mark it required. However, skip, filter, select, and orderby are left unexplained, and with 0% schema description coverage the description only partially compensates for the missing parameter documentation.

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 states a specific verb and resource: 'Get certificate chain details for a keystore entry.' It also distinguishes itself from the sibling get_keystore_entries by noting that it cannot list all certificates directly, preventing confusion between the two tools.

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?

Usage guidance is explicit: it requires hex_alias from a Key Pair entry in get_keystore_entries, and it warns that Certificate-type entries are rejected by CPI. It also clarifies a key limitation—'Cannot list all certificates directly'—so an agent knows when not to attempt listing via this tool.

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