campaigns_describe

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

With no annotations, the description must fully disclose behavior, but 'Get campaign details' reveals nothing about permissions, side effects, result scoping, or error conditions. It is purely a statement of action without any behavioral context.

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 brief, which is concise, but it is under-specified. It conveys a basic purpose but does not add details that could justify its short length. It earns a middle score for being front-loaded but lacking substantive content.

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?

Given the tool's simplicity (one param, output schema present), the description could be minimal but still needs to help select it among many siblings. The lack of usage guidance and parameter explanation makes it incomplete for practical invocation.

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 one required parameter 'campaign_id' with no description and 0% schema description coverage. The description does not explain what campaign_id represents, how it is used, or any constraints, leaving the agent with no additional semantic value beyond the parameter name.

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 uses a specific verb 'Get' with a resource 'campaign details', clearly indicating the tool retrieves campaign information. However, it does not distinguish itself from sibling tools like campaigns_list or campaigns_get_state, which could also retrieve campaign-related data.

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. The sibling tools include several campaign-related operations (list, get_state, etc.), but the description gives no context or exclusions, leaving the agent to infer when 'details' is the right choice.

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