ncloud_dataforest_get_account_detail

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

ReadOnlyHint annotation already declares it's read-only. The description adds the specific inclusion of HDFS quotas, which provides some context beyond annotations. However, it does not disclose error behavior or other side effects.

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 a single sentence that directly conveys the purpose. It is concise and front-loaded with key information, but could be slightly expanded without becoming verbose.

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 simple tool (one parameter, read-only, no output schema), the description is somewhat adequate. However, it omits details on the exact output structure beyond quotas, which would help an agent understand the return value.

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%; the schema already describes the 'id' parameter as a Base62-encoded UUID. The description does not add any additional meaning or constraints beyond the schema.

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 (get detailed information) and the resource (Data Forest account), including specific content (HDFS quotas). It distinguishes from sibling tools like ncloud_dataforest_list_accounts by focusing on a single account's detail, though not explicitly said.

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 on when to use this tool versus alternatives (e.g., list_accounts, check_account_resource). No prerequisites or context provided, such as needing an account ID from a prior list call.

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