buscar_entidades_campo

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

No annotations are provided, so the description must carry the burden. It states the tool is a search operation returning entities supporting custom fields, but lacks details on pagination, authentication, or what exactly is returned beyond examples. It is adequate but not rich.

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 concise (two sentences plus notes) and front-loads the main purpose. Minor formatting improvement could integrate notes, but overall efficient.

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 list retrieval tool with one optional parameter and no output schema, the description covers main purpose and usage. However, it does not explain pagination behavior or return format, leaving gaps.

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?

Input schema has one parameter 'pagina' with 0% description coverage. The tool description does not mention this parameter or its purpose, failing to add value beyond the schema's default and type.

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 verb ('buscar' - search) and resource ('entidades disponiveis para campos personalizados') with specific purpose: obtain EntityId for custom fields. It distinguishes from sibling tools like 'buscar_campos' and 'salvar_campo' by focusing on entity retrieval.

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 explicitly tells when to use: 'Use para obter o EntityId ao criar campos personalizados.' It provides context but does not explicitly mention when not to use or compare with alternatives, though the purpose is sufficiently specific.

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