Novedades para un perfil (ayudas + BOE)

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: only non-closed ayudas and only items within the recent day window. It does not say how results are ordered or whether there are caps on returned items.

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, front-loaded with what is returned and the scope constraint (open ayudas, recent days). The closing audience list (autónomo, pyme, gestoría, asociación) is somewhat expendable but cheaply sets the context.

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, and with five all-optional parameters the description never states the default behavior when nothing is supplied (e.g. does an empty 'palabras' return all topics for the last 7 days?). It is adequate for the aggregation concept but leaves the zero-argument invocation ambiguous.

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% and three parameters carry enums with documented meanings, so the schema does the heavy lifting. The description reinforces that 'palabras' means the profile's topics and that results cover both sources, but adds no format or default-behavior detail beyond the schema.

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 combined resource: a digest of newly published ayudas (only those still open) plus BOE items matching a profile's topics. This is clearly distinguishable from siblings like ayudas_buscar or boe_sumario_dia, which are single-source lookup tools. It stops short of explicitly naming those siblings as the alternative, so it is clear but not maximally differentiated.

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?

'Pensado como boletín semanal' implies a recurring digest use case, which is useful context. However, it gives no explicit when-not guidance nor points to ayudas_buscar/boe_buscar for targeted single-source queries, leaving the agent to infer the boundary.

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