inei_search_indicators

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

No annotations provided, so description carries burden. Does not explicitly state it is read-only or non-destructive, but as a search tool this is implied. Could be more transparent about any rate limits or authentication needs.

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?

Reasonably concise with three short paragraphs. First sentence is clear. Could be slightly more concise by removing the list of example searches from the description, but overall well-structured.

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 no output schema and moderate complexity, description adequately covers tool purpose, return values, and relationship to sibling tool. Pagination via offset/limit is explained in schema, not repeated.

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 coverage is 100%, so baseline is 3. Description adds value by clarifying return fields (id_indicador, name, ruta) and providing usage context beyond schema parameter descriptions.

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?

Clearly states the tool searches INEI thematic indicators by keyword, specifies the database source and indicator types. Distinguishes from sibling tools like inei_browse_topics which likely uses browsing instead of keyword search.

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?

Provides example searches and explains how to use the returned id_indicador with inei_get_indicator_data. Lacks explicit guidance on when not to use this tool, but overall helpful context to guide the agent.

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