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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior. The description usefully adds the auth posture ('Pública, sin cuenta'), but the returned field list is redundant with the existing output schema, so the net addition beyond structured data is modest.

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?

Compact and front-loaded: the core action and scope come first, then access requirements and the follow-up pattern. No filler sentences, though it is dense and mixes return-shape detail that the output schema already covers.

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?

With an output schema present, rich annotations, and a single fully documented parameter, the description only needs to add scope, access, and chaining. It covers all three, though it omits any differentiation from the overlapping search siblings.

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?

One parameter at 100% schema coverage, and the schema already documents it as 'Búsqueda en lenguaje natural'. The description repeats that phrasing without adding format, length (maxLength 200), or query-construction guidance, so it is baseline.

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?

States a specific verb and resource: natural-language search over BOE judicial auctions, plus the ChatGPT deep-search compatibility. However, it does not distinguish itself from the very similar sibling `buscar_subastas` (or `buscar_por_codigo`), leaving the agent to guess which search entry point applies.

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?

It implies usage context ('Pública, sin cuenta') and hints at a follow-up path ('Cada resultado se lee completo por su id'), which routes toward a detail/fetch tool. But it never says when to choose this over `buscar_subastas` or `similares`, so the selection guidance is only implied.

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