ncloud_ncs_get_object_attributes

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds context about the single-call efficiency and enumerates the attributes returned, which goes beyond the annotation. It does not contradict annotations, and the extra detail about attribute selection is useful.

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, information-dense sentence. It is front-loaded with the purpose and includes the HTTP endpoint and header name without extraneous words. Every part contributes to understanding the tool's function.

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 read-only tool with a simple parameter set (2 required, 6 total) and high schema coverage, the description is sufficiently complete. It covers what the tool does and the attributes it can return. Pagination details are not mentioned, but they are fully documented in the schema (maxParts, partNumberMarker), so nothing critical is missing.

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 100%, so all six parameters have descriptions. The tool description adds minimal new meaning beyond the schema—it lists the attribute enum and mentions the default set, which is already in the schema. Since the schema carries the burden, a baseline 3 is appropriate.

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 tool's function: getting selected attributes of an object. It names specific attributes (ETag, ObjectSize, StorageClass, Checksum, ObjectParts) and mentions the HTTP endpoint, distinguishing it from tools that fetch object content (ncloud_ncs_get_object) or headers (ncloud_ncs_head_object). The verb and resource are unambiguous.

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 does not explicitly mention when to use this tool versus alternatives. It implies efficiency ('in one call') and the attribute list differentiates it, but there is no explicit guidance like 'use this instead of head_object for specific attributes.' An agent would infer usage from the name and description, but it is not explicitly stated.

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