ncloud_dataflow_get_execution_interval

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

Annotations already set readOnlyHint=true, so this is a safe read operation. Description adds that it returns dashboard statistics grouped by interval, but lacks details like authentication needs, rate limits, or behavior with invalid inputs.

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?

Single sentence that front-loads the purpose and output. No redundant information. Every word contributes to understanding.

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?

Given no output schema, description only says 'Returns execution counts grouped by time interval', which is vague. Lacks details about output structure or possible group dimensions. Adequate for a simple stats tool but could be more helpful.

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 clear descriptions for endTime and startTime. Description does not add additional meaning beyond the schema, such as inclusivity of time range or format examples. Baseline score of 3 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?

Description clearly states 'Get job execution count statistics for Data Flow dashboard' with verb 'Get' and specific resource. 'Returns execution counts grouped by time interval' further clarifies the output. Distinguishes from sibling 'ncloud_dataflow_get_execution_times' which likely returns actual execution times.

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 guidance on when to use this tool vs alternatives. Does not mention when not to use it or any prerequisites. Sibling tools with similar purposes exist but no comparison is provided.

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