aya_framework_skills_buscar

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully reveals that the tool does not open the entire pack, but it does not state read-only status, whether 'pesadas' are excluded by default, or what happens when no skills match.

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 front-loaded sentence with no filler: verb, target, criteria, and key constraint are all present. Every clause contributes actionable information.

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?

The core search behavior is clear, but with no output schema and no annotations, the agent still has to guess the return shape, the semantics of the optional parameters, and how this tool differs from content-oriented siblings. It is minimally adequate for a simple search tool, but not fully complete.

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?

With 0% schema description coverage, the description needed to explain consulta, limite, and incluirPesadas, but only weakly implies that consulta is the search query. It never clarifies what 'pesadas' means or how incluirPesadas changes the search, leaving a material gap.

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 names a specific verb ('Busca' = searches), a resource ('skills relevantes'), and explicit search criteria ('por metadados, gatilhos e caminho'). The closing phrase 'sem abrir todo o pack' distinguishes it from heavier pack-level tools, so an agent can tell it apart from siblings like aya_framework_pack_montar.

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 implies the right moment to use it: a lightweight search over skill metadata when you want to avoid opening the whole pack. It does not name alternatives such as aya_framework_buscar_conteudo or state when not to use it, so the routing guidance is inferred rather than explicit.

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