aircall_get_campaign

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds a useful constraint (one active campaign per user) but does not disclose other behaviors such as return format or behavior when no campaign exists. This is consistent with the baseline for annotated read operations.

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 two short sentences that are front-loaded with the main purpose and immediately provide a key constraint. There is no wasted language, making it highly efficient.

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 getter with one parameter, readOnlyHint annotation, and no output schema, the description is adequate. It explains what is returned (the active campaign) and the uniqueness rule. It could optionally mention the response when no campaign exists, but that is not critical for a straightforward retrieval 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?

The input schema has 100% coverage for user_id, including a clear description that it targets the user whose dialer campaign to retrieve. The tool description adds no extra parameter information, so it relies on the schema, which is fully sufficient.

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 action ('Get') and the specific resource ('a user's active power dialer campaign'). It also adds the unique constraint that each user has at most one active campaign, which distinguishes it from other campaign-related operations like create or delete.

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 noting that each user has at most one active campaign, making it evident when this tool is appropriate. However, it does not explicitly name alternatives or state when not to use it, so it lacks a full exclusion clause.

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