bolna_get_agent

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

No annotations are present, so the description must convey behavioral traits. It states 'retrieve', indicating a read operation, but fails to disclose error handling (e.g., 404 if agent not found), authentication requirements, rate limits, or whether any side effects occur. The description is minimally transparent.

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, front-loaded sentence with no wasted words. Every part is essential: verb, resource, identifier. Highly concise.

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?

For a simple retrieval tool with one parameter and no output schema, the description is adequate but lacks depth. It does not mention the structure of the returned configuration, error states, or permissions. It meets the minimum threshold but leaves gaps for an agent to infer.

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 description coverage is 100% (agent_id is fully described). The tool description does not add any new meaning beyond the schema; it merely restates the parameter. Baseline score of 3 is appropriate since the schema already provides sufficient parameter documentation.

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 uses a specific verb 'Retrieve' and clearly identifies the resource as 'full configuration of a specific Bolna agent by its ID'. It effectively distinguishes itself from sibling 'list' tools like bolna_list_agents by specifying retrieval of a single agent's full configuration rather than a summary list.

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 needing the full configuration of one agent, but it does not explicitly state when to use this tool over alternatives (e.g., bolna_list_agents for summaries, bolna_get_batch for batches). No guidance on conditions or exclusions is provided.

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