bamboo_get_deployment_result

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

No annotations are provided, so the description carries full burden. The verb 'Get' strongly implies a read operation with no side effects, but the description does not explicitly confirm this or disclose any potential behavioral traits (e.g., error handling, permissions, rate limits). It is minimally adequate but lacks depth.

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 extremely concise at 10 words, front-loading the verb and resource. Every word earns its place with no redundancy or filler.

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 has 3 parameters, no output schema, and no annotations, the description is minimally complete. It explains the main purpose but lacks details on return value structure, error behavior, or log inclusion nuances. For a simple retrieval tool, it is adequate but could be improved.

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%, so baseline is 3. The description adds 'with optional logs', which hints at include_logs and max_log_lines parameters but does not add meaning beyond the schema descriptions. No additional semantic value is provided.

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 'a specific deployment result', and distinguishes from sibling tools like bamboo_get_deployment_results (plural, list) and bamboo_get_build_result (different resource). The mention of 'optional logs' adds specificity.

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?

The description implies usage for retrieving a single result but does not explicitly state when to use this tool versus alternatives like bamboo_get_deployment_results (list) or bamboo_get_build_result (build). No exclusions or context beyond the singular noun are provided.

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