ncloud_sens_send_push

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

No annotations exist, so the description carries the full burden. It states it sends a notification (a write operation) and mentions an env variable requirement. However, it fails to disclose any other behavioral traits such as what happens on failure, rate limits, idempotency, or response format. The description is too brief for a send operation with no output schema.

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 very short (two sentences) and front-loaded with the primary action. It is concise, but for a tool with complex nested parameters, it could benefit from a brief overview of usage. Still, it avoids unnecessary fluff.

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?

No output schema exists, increasing the need for description completeness. The description does not mention return values, error cases, or how the push notification is sent (e.g., to all devices? async?). Given the complexity of the input schema and the large sibling list, this description is insufficient for an agent to understand the full context.

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% with detailed descriptions for all parameters and nested objects. The description adds no additional parameter explanation beyond what the schema provides. Baseline 3 is appropriate as the schema handles semantics adequately.

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 'Send push notification via SENS', which is a specific verb and resource. It distinguishes from siblings like 'send_sms' and 'send_alimtalk' by focusing on push notifications, making the tool's purpose 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 includes a prerequisite (environment variable requirement), which is helpful. However, it does not provide guidance on when to use this tool versus alternatives (e.g., when to send push vs SMS). No when-not or alternative suggestions are given.

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