ncloud_sourcebuild_start_build

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

Description does not add behavioral details beyond what annotations already provide (idempotentHint=true, destructiveHint=false). Annotations cover safety profile adequately.

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 is concise and front-loaded. No wasted words, though could include a brief note on return value without losing conciseness.

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 simple input (one param, no output schema) and sibling tools covering lifecycle, the description is complete enough. Could mention asynchronous behavior or build ID return.

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% (one parameter described). Description adds no extra meaning beyond the schema's 'Project ID to build'. Baseline 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 states 'Start a build for a SourceBuild project' with a specific verb and resource. It clearly distinguishes from sibling tools like ncloud_sourcebuild_create_project (create) and ncloud_sourcebuild_cancel_build (cancel).

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, no mention of prerequisites (project must exist), or when not to use it (e.g., if build already in progress).

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