get_campaign_logs

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

No annotations provided, but description implies read operation (get logs). Does not explicitly state read-only or any side effects, but adequate given the 'get' nature.

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?

Two concise sentences, but includes a stray '[query]' placeholder. Efficient but not perfectly clean.

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?

Sufficient for a logging tool with pagination implied by parameters. Lacks mention of return format or log details, but acceptable without output schema.

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?

All parameters are documented in schema (100% coverage). Description adds minimal value beyond mentioning campaign specificity. Page and limit are not elaborated.

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?

Describes retrieving progress and sending logs for a specific campaign, differentiating from get_campaign. However, language mix (Spanish/English) and lack of explicit differentiation from other log tools slightly reduces clarity.

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 on when to use this tool vs alternatives (e.g., get_campaign, other log tools). The description only states what it does.

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