ncloud_pca_sign_sub_csr

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

The description claims a write operation ('Sign...to issue') but the annotations declare readOnlyHint: true. This is a direct contradiction. Additionally, the description does not disclose side effects, permissions, or return values typical of a signing operation.

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 with no extraneous information. Every word is necessary.

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?

Given the tool is a CA signing operation with no output schema and a contradictory annotation, the description lacks critical information such as return format, prerequisites (e.g., parent CA must exist), and whether the signed certificate is stored or returned. The contradiction further degrades completeness.

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 baseline 3. The description does not add meaning beyond schema descriptions; e.g., it does not elaborate on caTag, csrPem format, or period constraints.

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?

Description clearly states the action ('Sign a Sub CA CSR using this CA') and the result ('issue an intermediate CA certificate'), distinguishing it from sibling tools like ncloud_pca_sign_end_csr which signs end entity CSRs.

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 for creating an intermediate CA from a sub CA CSR, but does not explicitly state when to use this tool versus alternatives (e.g., sign_end_csr for end entities) or provide exclusion criteria.

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