iaas_get_certificate_info

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile needs no restating. The description adds nothing beyond the path – no auth requirements, no behavior on an unknown id (404 vs empty), and no note about what object is returned, which matters since there is no output schema.

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?

Two short lines, front-loaded with the verb+resource and no filler. The second line only restates the annotation title endpoint, so it is near-waste but not harmful.

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 read tool with no output schema, the description should at least say what a certificate record contains or how it relates to endpoints/cloud accounts. Instead it gives only the raw HTTP route, leaving the agent to guess the payload shape and the domain object.

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 100%, so both the id path parameter and the apiVersion date parameter are documented in the schema, setting the baseline at 3. The description contributes nothing further – notably it does not clarify the id, whose schema text is a mismatched copy-paste ('ID of the EndpointCreationTaskState').

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?

"Get certificate info" states a clear verb plus resource, and the REST path confirms it is a fetch-by-id for a single certificate. It does not distinguish itself from the many other iaas_get_* retrievers (or provider_get_certificate) or say what 'info' contains, so it stops short of a 5.

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 indication of when to call this versus a list endpoint or the sibling provider_get_certificate. There are no prerequisites, exclusions, or alternative-routing guidance anywhere in the text.

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