ise_openapi_cert_system_get

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

No annotations are provided, so the description should carry the behavioral burden. The description names the HTTP endpoint (GET /api/v1/certs/system-certificate/{hostName}/{id}) which is transparent about the operation. However, it doesn't disclose what the response looks like, whether it returns the full cert chain, or any security/permission requirements for accessing system certs.

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 compact single sentence that packs the resource scope, the specific verb, and the endpoint. It's efficient with zero filler. The '[Certificates]' category prefix helps with navigation. Slightly more context could be warranted but nothing extraneous is present.

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 single-item GET with 100% schema coverage and no output schema, the description is mostly adequate. However, it lacks any note about return format, what the certificate data contains, or relationship to the delete/import/export sibling tools. Given the simplicity of the tool, this is acceptable but leaves room for more helpful context.

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 schema already documents all parameters. The description adds little beyond the schema—it references hostName and id in the endpoint path, and the deployment parameter has rich schema guidance (pointing to ise_list_deployments). Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states 'Get system certificate of a particular node by ID' with the specific verb (Get) and resource (system certificate of a node). It's distinguished from siblings by the '[Certificates]' prefix and 'system-certificate' specificity, though it doesn't explicitly differentiate from ise_openapi_cert_system_list/delete/import/export 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?

The description implies usage (GET a specific certificate by ID on a host), and the schema's deployment parameter adds guidance by referencing ise_list_deployments. However, there's no explicit when-to-use vs alternatives statement, no exclusion criteria, and no mention of when to use the list tool instead of this get tool.

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