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

With no annotations provided, the description carries the behavioral burden. It clearly indicates a read-only listing operation and specifies the returned data fields, including the useful detail that JWKS fetch age is included. While it does not discuss authentication or side effects, 'List' and the field list are sufficient for this non-destructive tool.

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, front-loaded sentence with no filler. Every element adds value: the operation, the scope, and the exact returned fields.

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 simple one-optional-parameter list tool with no output schema, the description provides enough information about what will be returned and the tenant scope. It does not detail response formatting or pagination, but those are minor omissions given the simplicity of 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?

Schema description coverage is 100%, so the input schema fully documents tenant_key, including when it is required and how it interacts with the Authorization header. The description adds no parameter-level detail beyond the schema, matching the baseline for high schema coverage.

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 a specific verb ('List') with a clear resource ('this tenant's registered OAuth issuers') and names the key returned fields. This clearly distinguishes it from the sibling tools host.oauth.issuer_set and host.oauth.issuer_remove, which are mutation operations.

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 listing verb and tenant scope imply this is the read-oriented counterpart to issuer_set/issuer_remove, but the description does not explicitly state when to use this tool instead of those alternatives. There is no direct when/when-not guidance, so usage is mostly inferred from the resource name and siblings.

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