sdcloud_list_device_ca_certificates

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

With no annotations, the description should disclose basic behavior (e.g., read-only, pagination, side effects). It only states 'list' without mentioning pagination, filtering, or that it returns a list. This is insufficient for a mutation-aware agent.

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?

Single sentence, no redundancy. Perfectly concise for the tool's simplicity.

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?

While simple, the description omits mention of pagination (from/size) and filtering capabilities. For a list tool, this context would be helpful. No output schema means the description could clarify return value, but it doesn't.

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 80%, so most parameters are already described. The description adds no further parameter info, but this is acceptable given the schema's adequacy.

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 action (list) and resource (CA certificates) with a specific scope (installed on a specific device). This distinguishes it from sibling tools like sdcloud_list_ca_certificates.

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 guidance is provided on when to use this tool versus alternatives (e.g., sdcloud_list_ca_certificates or sdcloud_list_local_certificates). The agent must infer from the name alone.

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