ncloud_list_pipeline_history

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

Description does not contradict readOnlyHint annotation. However, it adds no extra behavioral details (e.g., pagination behavior, ordering, error states) beyond what the schema and annotations already provide.

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 with no wasteful words. Front-loaded with the action ('Get execution history list'). Could be slightly longer to include key constraints, but remains 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?

Given no output schema, the description should hint at return format. It does not mention that pagination parameters are available or that the list is returned in a specific structure. Lacks completeness for a list operation.

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%, so the schema fully documents parameters. Description adds contextual value by mentioning 'pipeline' but adds no new semantic information about parameters.

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 execution history list for a SourcePipeline pipeline', specifying verb, resource, and scope. It distinguishes from sibling 'ncloud_get_pipeline_history_detail' by indicating it returns a list rather than a single detail, but does not explicitly differentiate.

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 like 'ncloud_get_pipeline_history_detail' or when pagination is needed. Agent must infer usage from context.

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