ncloud_get_policy_resources

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context about scope ('currently assigned to') and the resource types, but does not disclose additional behavioral details such as pagination, response shape, or whether the list includes inherited assignments. With annotations handling the read-only trait, a 3 is appropriate.

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 sentences with no filler. The primary action and resource scope are front-loaded, and the usage guidance is integrated naturally. Every sentence earns its place.

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?

For a simple read-only tool with one well-documented parameter, the description is complete. It states what is listed, that the listing reflects current assignment, and the practical context for when an agent should call it. The lack of an output schema is compensated by the clarity of the expected result.

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 sole parameter policyId is already documented in the schema, including a pointer to ncloud_list_policies. The description adds no new semantics about the parameter beyond what the schema provides, so it meets the baseline without exceeding it.

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 uses a specific verb ('List') and resource ('resources a policy is currently assigned to'), enumerates the resource types (sub accounts, groups, roles), and clearly distinguishes this from related policy tools such as ncloud_get_policy_detail or ncloud_list_policies. An agent can understand exactly what this tool returns without ambiguity.

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 explicitly states when to use this tool: 'Use this before deleting or editing a policy to see who is affected.' This gives clear contextual guidance, though it does not name specific alternative tools or explicitly say when not to use it.

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