get_pickup_rates

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

Since no annotations are provided, the description bears full responsibility. It accurately conveys the read-only nature of the tool and what it returns. It does not mention authorization or rate limits, but for a simple query tool, the description is sufficiently 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 concise: two sentences with no wasted words. It front-loads the main purpose and includes the key output fields, making it easy to scan quickly.

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?

The tool has 5 optional parameters and no output schema, so the description should cover return structure. It lists the returned metrics (total calls, answered calls, pickup rate) and implies a per-phone-number list. Some additional detail about response format would be helpful, but it is fairly complete given the simplicity of the tool.

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 coverage is 100%, so baseline is 3. The description does not add any parameter-specific information beyond what is already in the schema. It mentions 'by phone number' but the parameters are about dates, agent, campaign, and call type, without explaining how they affect results.

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 it gets pickup rate by phone number, listing the returned metrics (total calls, answered calls, pickup rate) and the use case for optimizing caller IDs. This is specific and distinguishes it from many sibling tools that focus on agents, campaigns, or versions.

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 provides clear context by stating it is useful for optimizing caller IDs, but does not explicitly mention when not to use it or compare with alternative tools like get_phone_number_trends. The guidance is implied but lacks exclusions.

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