list_guides

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

No annotations are provided, so the description is the sole source of behavioral disclosure. It only states the basic listing action and does not reveal pagination behavior, the effect of the 'limit' parameter, the meaning of 'poblacion_id', or the response structure. It also does not explicitly confirm the operation is read-only.

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 a single concise sentence with no redundant text, which is positive. However, it is under-specified rather than efficiently structured, omitting critical information that an agent would need to use the tool correctly.

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?

For a simple listing tool with optional parameters and no output schema, the description lacks essential context: no return format, no pagination details, no explanation of the 'poblacion_id' filter, and no distinction from other listing tools. This makes it insufficient for confident selection and invocation.

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 contains two optional parameters with no descriptions, and the tool description mentions neither 'limit' nor 'poblacion_id'. With 0% schema description coverage, the description wholly fails to compensate by explaining parameter meaning or usage.

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's purpose: to list published guides in Rovee, using a specific verb ('Lista') and resource ('guías'). It distinguishes from sibling listing tools by resource type, though it doesn't elaborate on what 'guides' are or how they differ from other content.

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 offers no guidance on when to use this tool versus alternatives like list_blog_posts or list_pois. It neither states specific use cases nor mentions any conditions where a different listing tool should be preferred.

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