ise_openapi_cert_csr_list

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It specifies the endpoint (GET /api/v1/certs/certificate-signing-request) and that it retrieves CSRs from PAN (Policy Administration Node), which adds useful context. However, it doesn't disclose pagination behavior, return format, max result limits, or whether anything is mutated. For a fetch tool this is moderate but still leaves gaps.

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 concise line, effectively front-loaded with the purpose. No wasted words. However, it could be argued it's slightly under-specified in terms of behavioral content, but as a structure it's efficient.

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 list/fetch tool with 0 required parameters and no output schema, the description provides the essence. The endpoint is documented, the PAN scope is clarified, and the deployment targeting is handled well. However, the pagination params (page/size) are unexplained, and with no annotations and no output schema, the agent gets limited behavioral context about what to expect from the response.

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 coverage is 33%, with only the 'deployment' parameter having a description. The page and size parameters lack descriptions entirely, and the description text doesn't explain them either. The deployment parameter description is actually quite good, explaining format choices and pointing to ise_list_deployments. With 1 of 3 parameters helpfully documented, this is slightly above baseline but the page/size semantics remain undocumented.

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 the specific verb+resource: 'Get all Certificate Signing Requests from PAN' with the API endpoint path. The tool name itself (ise_openapi_cert_csr_list) is highly descriptive, and the category prefix '[Certificates]' plus the GET endpoint make purpose clear. It doesn't explicitly distinguish from siblings, but the focused naming and the 'all... list' phrasing differentiate it from get/delete/import variants among cert siblings.

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 when-to-use guidance is provided. The description doesn't explain when to use this list tool versus the other certificate tools (ise_openapi_cert_system_list, ise_openapi_cert_trusted_list) which are the closest alternatives. No exclusions, prerequisites, or context about where CSR listing fits in a workflow are given.

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