ise_openapi_cert_trusted_get

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 behavioral disclosure. Yet it only states the endpoint and offers no behavior details: no mention that this is a safe read-only operation, no return format, no error cases (e.g., not-found), no authentication requirements. For a GET-style fetch with zero annotation coverage, this is a significant transparency gap.

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 terse line that captures the endpoint but reads as an auto-generated API label rather than a composed description. It's compact with no waste, but it's arguably under-specified rather than truly concise—there's room for useful content without bloat. Front-loading is fine but the content is minimal.

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 fetch-by-ID tool with no output schema and no annotations, the description should explain what the agent gets back, any error conditions, and relation to list/update/delete siblings. It does none of this. The 100% param coverage helps, but behavioral and output context is entirely absent, making the tool weakly self-describing for an agent navigating a large sibling set.

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%, with the two parameters (id, deployment) documented in the schema. The description adds nothing beyond the schema about these parameters. The deployment parameter has a helpful inline explanation in the schema (deployment names/format). Per the baseline rule, a 3 is appropriate since the schema does the heavy lifting and the description contributes no additional parameter meaning.

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 the resource ([Certificates]), verb (Get), and specific item (Trust Certificate By ID) with the exact API endpoint. It distinguishes itself from sibling cert tools (system/trusted/csr lists and mutations) by being the specific 'get by ID' operation for trusted certificates. However, it doesn't explicitly note what distinguishes it from 'cert_trusted_list' beyond the implied 'by ID' scope.

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 is essentially an API endpoint label rather than usage guidance. It implies usage (fetch a trusted certificate by ID) but provides no explicit when-to-use vs alternatives, no exclusions, and no context about prerequisites (e.g., needing to know an existing certificate ID first, perhaps from a list call). Without sibling differentiation, the agent must infer context.

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