get_campaign

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

Annotations already declare readOnlyHint=true, so the tool is known to be read-only. The description adds value by specifying that the detail includes 'envíos (jobs) por contacto y su estado' which provides behavioral context beyond what annotations offer.

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 sentences, no filler. The first sentence conveys the core purpose and what is included. The second sentence provides immediate actionable guidance. 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?

Given the simplicity of the tool (one required parameter, no output schema), the description adequately covers the main aspects: what it does, what it returns, and how to get the input. It does not address error conditions, but that is not critical for a read-only 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'por su UUID' which explains the purpose of the campaign_uuid parameter. However, no format or constraints are provided; the parameter is just a string with minLength 1. The description is minimal but sufficient for a single required parameter.

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 states 'Obtiene el detalle de una campaña por su UUID, incluyendo los envíos (jobs) por contacto y su estado.' This clearly identifies the verb (get), resource (campaign detail), and scope (including jobs per contact and status). It also distinguishes from sibling list_campaigns.

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 explicitly says 'Usa list_campaigns para descubrir los UUID.' This gives a direct usage guideline, telling the agent to use list_campaigns first to get the UUID. It implies when to use this tool: when you have a specific UUID and need detail.

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