bolna_get_execution

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns transcript and recording URL, which suggests read-only behavior. However, it does not explicitly state that no modifications are made, nor does it cover authentication needs or rate limits. For a simple read operation, the disclosure is adequate but not comprehensive.

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 with no unnecessary words. It front-loads the purpose and includes key details (transcript and recording URL). Every element is essential.

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 one parameter, no output schema, and no annotations, the description is fairly complete. It specifies what the tool returns (transcript and recording URL). However, it does not list all possible fields in 'full details', which could be slightly more explicit. Overall, it is sufficient for a simple retrieval 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 100% description coverage for the single parameter execution_id. The description does not add any additional meaning beyond the schema; it only repeats the purpose of the tool. Since schema coverage is high, the baseline is 3, and the description does not improve upon it.

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 tool retrieves full details of a call execution, specifying it includes transcript and recording URL. The verb 'Retrieve' and resource 'full details of a call execution' make the purpose specific and distinguishable from sibling tools like bolna_list_agent_executions and bolna_get_batch_executions.

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 when one needs full details of a specific execution, but it does not explicitly state when to use this tool versus alternatives like bolna_get_batch_executions or bolna_list_agent_executions. No when-not or alternative guidance is provided.

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