ncloud_pca_get_sub_csr

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

Annotations already declare readOnlyHint=true, so the description's 'Get' is consistent. The additional behavioral detail 'Only available for unsigned Sub CAs' adds value beyond annotations, clarifying a key constraint. No contradictions. Lacks details on idempotency or failure modes, but for a read operation this is sufficient.

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 sentences with no redundant words. The action is front-loaded ('Get the CSR...'), and the constraint is appended concisely. Every sentence contributes essential information.

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 has one parameter, no output schema, and annotations cover read-only behavior, the description is complete. It explains what the tool does, the condition, and the schema covers the parameter. No missing necessary information for selection and correct invocation.

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% with a single parameter 'caTag' described as 'CA tag value of the Sub CA'. The tool description does not add any additional meaning or context beyond what the schema provides. Baseline is 3, and no extra value is contributed.

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 'Get the CSR... of a Sub CA for external signing', specifying the verb and resource, and distinguishes from siblings by mentioning 'Sub CA' and 'external signing'. It also adds a condition ('Only available for unsigned Sub CAs'), providing precise 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 implies when to use: when you need the CSR of an unsigned Sub CA for external signing. It does not explicitly name alternatives or state when not to use, but the condition 'only available for unsigned Sub CAs' provides clear usage context. Sibling tools like ncloud_pca_sign_sub_csr handle signing, so the usage boundary is implied but could be more explicit.

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