ssl_get_cert_files

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds an important security-relevant behavioral note: 'The private key is returned by DirectAdmin — treat the response as secret.' This goes beyond the schema and helps the agent handle the response safely.

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 short and front-loaded with the core purpose, followed by a critical security warning. The Args list is somewhat redundant with the schema but is compact and does not add meaningful bloat.

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?

The description gives enough to understand the basic operation and secret-handling requirement, and an output schema exists to cover return structure. However, it lacks usage guidance, a pointer to how cert_id should be obtained, and more substantive parameter semantics, leaving noticeable gaps for an agent selecting and invoking the tool.

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 0%, so the description must compensate. However, the Args section mostly restates the schema titles: 'domain: Domain' and 'cert_id: Certificate id' add no real meaning. Only 'impersonate: Owning user' adds a small clarification. No format, source, or relationship between domain and cert_id is explained.

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 opens with a specific verb and object: 'Download certificate + chain + key files for a domain cert id.' This clearly distinguishes the tool from siblings like ssl_list_domain_certs (listing), ssl_upload_cert_files (uploading), and ssl_server_files (server-level files), even without naming them.

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 phrase 'Download... for a domain cert id' implies this tool is for retrieving cert files, but there is no explicit guidance about when to prefer it over related SSL tools or when not to use it. No alternatives or exclusions are mentioned.

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