list_campaigns

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

With no annotations, the description must disclose behavioral traits. It only mentions 'obtiene todas' (gets all), but fails to clarify if this is a read-only operation, whether pagination exists, or if there are any side effects. The agent is left to assume it is safe.

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 short but includes the unclear '[query]' artifact, which harms conciseness. It could be trimmed to the first sentence without losing meaning.

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?

No output schema exists, so the description should explain what the tool returns (e.g., list of campaign objects, their fields). It only says it 'gets' campaigns. Given the many sibling campaign tools, more detail is needed for the agent to understand the output format.

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 no parameters (empty object), so schema coverage is 100%. However, the description introduces the unclear '[query]' which does not match the schema, potentially confusing the agent. Otherwise, no parameter info is needed.

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 that the tool lists all marketing campaigns, distinguishing it from siblings like get_campaign (single campaign) and create/delete/update. However, the trailing '[query]' is ambiguous and may cause confusion.

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 (e.g., get_campaign for a specific campaign). The description implies it returns all campaigns, but no context about filtering or opting for other list tools.

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