aya_regras_detectar_duplicadas

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

With no annotations provided, the description carries the behavioral burden. It clearly conveys a read-only detection operation, but it does not disclose whether the tool returns a list, a boolean, or a report, nor what happens when duplicates are or are not found.

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?

A single short sentence with no filler; the key scoping information ('em multiplos arquivos') is present and front-loaded.

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 zero-parameter detection tool, the description provides enough to understand its basic purpose. However, since there is no output schema and no annotations, the missing return-value or result-format information leaves a notable gap for an agent deciding whether the output will satisfy its need.

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 tool has zero parameters, so the empty schema already fully documents the input contract. The description correctly adds no parameter information, and the zero-parameter baseline of 4 applies.

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 uses a specific verb ('Detecta') and a precise resource ('IDs RN definidos em multiplos arquivos'), making the tool's scope clear. It is distinguishable from siblings like aya_regras_detectar_genericas and aya_regras_listar.

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?

Usage is implied rather than explicit: an agent can infer this tool is for finding RN IDs defined in more than one file. However, it does not name alternatives or state when not to use it, so explicit guidance is missing.

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