ncloud_dataflow_get_trigger

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

The readOnlyHint annotation indicates a safe read operation, which aligns with the description. No additional behavioral traits (e.g., required permissions, rate limits, or response size) are mentioned beyond what the annotation provides.

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, clear sentence that delivers the essential information without any unnecessary words. It is front-loaded and efficient.

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 getter with one required parameter, the description is nearly complete. It lacks details about the return value (e.g., what fields are included in 'detailed information'), but the presence of sibling tools and the generic name make the intent clear. Minor improvement could be adding output schema or link to documentation.

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 schema covers 100% of the single parameter (triggerId) with a description. The tool description does not add any further context about the parameter, such as how to obtain the ID or its format, so it meets the baseline but adds no value.

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 verb 'Get' and the resource 'detailed information of a specific Data Flow trigger', which precisely matches the tool name. Among sibling tools for Data Flow, there are list, create, delete, etc., and this get operation is clearly distinguished as a retrieval of a single trigger.

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?

No explicit guidance on when to use this tool versus alternatives like ncloud_dataflow_list_triggers or ncloud_dataflow_get_workflow. The description implies it is for fetching details after obtaining a triggerId, but does not state this directly or provide exclusion criteria.

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