ghl_agent_studio_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 for behavioral disclosure. It only says 'Get', which is already in the name, and adds no information about return format, error behavior, or permissions. The description provides minimal transparency beyond the verb.

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, short sentence with no redundant words. It's direct and easy to parse, earning high marks for 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?

For a simple single-resource retrieval, the description and schema provide enough to understand what the tool does and its inputs. However, without an output schema or annotation, it doesn't describe return values or edge cases, so it's not a 5.

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%, so the baseline is 3. The description adds 'by ID' which aligns with agentId, but it doesn't elaborate on locationId or parameter formats. The schema already documents both parameters, so the description contributes little extra semantic 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 'Get a specific AI agent by ID' uses a specific verb and resource, making it clear this retrieves a single agent. It distinguishes from the plural tool ghl_agent_studio_get_agents in the sibling 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 context is clear: use this when you have a specific agent ID and need that agent's details. It doesn't explicitly mention alternatives like get_agents for listing all agents, but the singular/plural distinction in sibling names provides implicit guidance.

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