ncloud_sens_get_sms_reservation_status

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

Annotations already declare readOnlyHint=true, so side-effect disclosure is not needed. The description adds the HTTP path and enumerates the exact possible status values (READY|PROCESSING|CANCELED|FAIL|DONE|STALE|SKIP), giving concrete expectations about the result. It does not describe the response structure or error details, but for a read-only status endpoint this is sufficient.

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?

A single sentence that front-loads the verb and resource, then provides the endpoint and the full status enum. No filler or repetition; every clause 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 status query, the description plus schema cover the essentials: how to get reserveId, how to determine/find serviceId, default behavior, and the statuses to expect. The lack of an output schema is partly mitigated by listing the status values, though the exact response field structure is not spelled out.

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% with rich parameter documentation (how reserveId is obtained, serviceId defaults via environment variables, discovery through ncloud_sens_list_projects, and the Forbidden interpretation). The description itself contributes no additional parameter semantics, so the baseline 3 for high coverage 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?

States the specific verb 'Get', the resource 'status of a scheduled SMS request', and includes the exact REST endpoint. The word 'scheduled' together with 'reservation' clearly distinguishes it from ncloud_sens_get_sms_status and ncloud_sens_list_sms_requests even without reading the siblings.

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 wording gives clear context: use this when you have a reservation ID from a scheduled SMS send and need its status. However, it does not explicitly contrast with alternatives such as ncloud_sens_get_sms_status for non-scheduled sends or ncloud_sens_cancel_sms_reservation for cancellation, so it stops short of full comparative guidance.

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