conversation_ai_get_agent

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the safety profile is covered. However, the description adds nothing beyond the annotations—no mention of the return payload, pagination, or any side effects. Since annotations carry the burden, the description's lack of added context results in a low score.

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 short, but this is under-specification rather than concise efficiency. It contains no useful information beyond the tool name, so it does not earn its place. The structure is minimal but lacks the substance needed to guide an agent.

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 get-by-ID tool without an output schema, the description should at least mention that it returns agent details or how the result is shaped. No such information is present. The presence of siblings like conversation_ai_search_agent and conversation_ai_get_action_by_id creates a need for differentiation that is unmet. The description is incomplete for helping an agent call this tool correctly.

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% because the single parameter agentId is documented as 'Conversations AI agent id'. This satisfies the baseline. The description does not elaborate further on the parameter, but the schema provides adequate meaning.

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 'Get Agent' essentially restates the tool name without adding any specific context about what the agent is or what fields it will return. It fails to distinguish this from siblings like conversation_ai_get_action_by_id or conversation_ai_search_agent. The verb and resource are clear but the description is tautological and does not explain the scope or nature of the retrieval.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of when to prefer get_agent over search_agent, how to obtain agentId, or any prerequisites. The description gives the agent no decision support.

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