cercar_viatges_alts_carrecs

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

No annotations are provided, so the description must carry the burden of behavioral transparency. It discloses the returned fields, but does not mention pagination behavior, rate limits, or whether the operation is read-only. The agent can infer it is a search (likely read-only), but details are missing.

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 concise with two short paragraphs: one for purpose and one for output fields. Every sentence adds value, with no fluff.

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 that an output schema exists (not shown), the description is reasonably complete. It covers the core purpose and output fields. However, it lacks explanation of the 'cerca_lliure' parameter and pagination, but these are documented in the 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?

Schema description coverage is 100%, so the baseline is 3. The tool description does not add meaning beyond the schema; it only lists output fields. No parameter usage details or syntax are added.

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 tool searches for trips abroad of high-ranking officials of the Generalitat, using a specific verb and resource. This distinguishes it from sibling tools like cercar_retribucions_alts_carrecs or cercar_directius_sector_public.

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 does not provide any explicit when-to-use or when-not-to-use guidance. It only states what the tool does, leaving the agent to infer context from the name. No alternatives or exclusions are mentioned.

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