ncloud_sourcebuild_get_project

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

The description is consistent with the 'readOnlyHint: true' annotation, as 'Get detailed information' implies a read operation. However, it does not add any behavioral context beyond the annotation, such as rate limits or data freshness. Since annotations sufficiently cover the safety profile, a score of 3 is appropriate.

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 sentence that is front-loaded and contains no wasted words. It is appropriately concise for a simple get operation.

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 the tool's simplicity (one parameter, no output schema), the description is adequate. It defines the action and parameter. However, without an output schema, a brief note on what 'detailed information' includes would improve completeness. Still, it meets the minimum viability for a read tool.

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 input schema has one parameter 'projectId' with description 'Project ID to query', and the schema description coverage is 100%. The tool description does not add any additional meaning beyond the schema, so the 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?

The description 'Get detailed information about a specific SourceBuild project' clearly states the verb ('Get') and the resource ('SourceBuild project'). It effectively distinguishes this tool from its sibling 'ncloud_sourcebuild_list_projects' which lists projects, while this gets a specific one. However, it does not elaborate on the nature of 'detailed information'.

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 is provided on when to use this tool versus alternatives like 'ncloud_sourcebuild_list_projects'. The description does not mention conditions for use or exclusions, which is a gap given the large number of sibling tools.

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