ncloud_sens_get_brandmessage_status

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

Annotations declare readOnlyHint=true, which is consistent with the description's 'Get' action. The description adds value by explaining the meaning of several status codes (0000, 3022, 3050, B004), providing useful context beyond the read-only hint. It does not contradict annotations and adds behavioral context about response interpretation.

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 concise and front-loaded: a single sentence stating the purpose and endpoint, followed by a compact list of status codes. Every part adds value without redundancy. It is well-structured and easy to scan.

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?

The description is adequate for a simple GET operation. It specifies the endpoint, status code meanings, and implies the full payload is returned. It does not describe the response schema, but given no output schema is defined, the description provides enough to understand the outcome. Minor gaps include lack of explicit return format, but this is not critical for a read-only status fetch.

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% and both parameters have descriptions. The description adds extra value for serviceId by explaining the default value, how to find it via ncloud_sens_list_projects, and the 'Forbidden' error scenario. This goes beyond the schema description, enriching the agent's understanding of the parameter's semantics.

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 retrieves a single Brand Message delivery result with its full payload, and includes the specific API endpoint. This distinguishes it from sibling tools like ncloud_sens_list_brandmessage_requests (list) and ncloud_sens_send_brandmessage (send).

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 state when to use this tool versus alternatives, but the purpose is clear enough that an agent can infer it for fetching a specific message status. There is no explicit 'when not to use' or mention of alternative tools, so it falls short of a 4.

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