get_agent

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 discloses that the tool returns 'full details' with a list of included fields, but does not mention error handling, permission requirements, or behavior on invalid IDs. The description adds some value beyond the schema but lacks complete 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, well-structured sentence of 23 words. It front-loads the primary action ('Get full details for a single agent by ID') and then lists the included fields. No unnecessary words or redundancy.

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 read tool with one parameter and no output schema, the description provides a sufficient overview of the returned data. It lists major categories, enabling an agent to determine usefulness. However, it could add error behavior details to be fully complete.

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?

There is only one parameter (agent_id) with a schema description already explaining its purpose ('The agent ID to retrieve'). The tool description adds minimal additional meaning beyond 'by ID', 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 clearly states the tool's purpose: retrieving full details for a single agent by ID. It lists specific return fields (voice config, model, prompt, language, call behavior, workflow type), distinguishing it from sibling tools like get_agents (which retrieves multiple agents) or get_agent_performance.

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 an agent ID is available, but does not explicitly state when to use this tool vs alternatives like get_agents or get_agent_prompt. No guidance on prerequisites or when not to use it.

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