bolna_get_disposition

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

No annotations are provided, so the description carries the full burden. It only says 'retrieve' with no details on whether it requires authentication, side effects (none expected for a read), or what the response contains, which is insufficient transparency.

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 concise sentence that gets to the point. It is front-loaded with the action and resource. While succinct, it could be slightly more informative 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 the simple schema and no output schema, the description is adequate but missing context about the return value (e.g., returns a full disposition object) and error handling. It covers the basic purpose but not edge cases.

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%, baseline is 3. The description does not add any meaning beyond the schema; it doesn't explain the purpose of agen_id or that disposition_id is required, so no extra value.

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 'Retrieve a single disposition by its ID' clearly states the verb (retrieve), resource (disposition), and method (by ID), which is specific and distinguishes it from siblings like bolna_list_dispositions or bolna_create_disposition.

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 usage is implied but not explicitly stated. The description does not mention when to use this tool versus alternatives (e.g., bolna_list_dispositions for multiple dispositions) or any prerequisites like having the disposition_id.

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