get_agents

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

With no annotations, the description should disclose behavioral traits. It only says 'get a list of agents' without mentioning pagination, sorting, limits beyond the schema, or any side effects. It doesn't state that it is read-only or describe how the limit parameter affects results. The description adds minimal value beyond the tool name and schema.

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 one short sentence with no redundant words. It is front-loaded and conveys the essential purpose immediately. No fluff or irrelevant details.

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-only list tool with one optional parameter and no output schema, the description is sufficiently complete. It states what is returned (list of agents). No additional context (e.g., authentication, rate limits) is strictly necessary given the simplicity, though it could mention default behavior of limit.

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% for the single optional parameter (limit). The description does not add any extra meaning about the parameter beyond what the schema provides. Baseline of 3 is appropriate since the schema fully documents the parameter.

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 a specific action ('get') on a specific resource ('list of agents') and clarifies that agents are operators in JivoSite. This distinguishes it from sibling tools like get_chats or get_contacts without ambiguity. The verb-resource combination is explicit and matches the tool name.

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 that this tool is for retrieving agents, but it does not explicitly mention when to use it over alternatives or provide any exclusion criteria. Sibling tools are inherently different (chats, contacts, messages), so context is clear, but there is no explicit usage guidance beyond the purpose statement.

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