ncloud_get_caller_identity

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

readOnlyHint=true already covers the safety profile, so the description adds real value on top: it discloses the underlying STS endpoint, the returned identity fields, and the meaning of each userType value (Customer/Sub/Role). No auth or rate-limit notes, but for a zero-argument read this is solid extra context.

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?

Front-loaded with the verb and resource, then the usage note; every clause carries information. The parenthetical endpoint and the userType breakdown are informative rather than filler, though the sentence is slightly dense.

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?

With no output schema, the description must carry the return-value burden, and it does by listing the three returned fields and interpreting userType. Annotations plus this text give an agent enough to call and interpret it correctly.

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?

The tool takes no parameters, and the input schema confirms an empty properties object with 100% coverage, so there is nothing for the description to compensate for. Baseline 4 applies.

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?

Specific verb 'Identify' applied to a precise resource ('the owner of the API key this server is using'), plus it enumerates the returned fields (id, loginAlias, userType). An agent knows exactly what this does without opening any schema.

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?

Gives a concrete when-to-use: to check whether a main-account-only API such as Certificate Manager 2.0 can be called with the current key. Clear operating context, though it names no sibling alternative or exclusion (there is arguably no meaningful one).

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