buscar_coluna

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

With no annotations, the description must carry the behavioral disclosure burden. It usefully reveals that matching is exact and case-insensitive, but it does not state whether the search is read-only, what happens with no or multiple matches, or how results are scoped. The output schema covers return structure, but other behavioral traits remain unstated.

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 sentence with no filler: the action is front-loaded and the only qualifier included ('sem diferenciar maiúsculas/minúsculas') is directly relevant to how the tool should be invoked. Every word earns its place.

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 one-parameter lookup tool, the description plus the input/output schemas cover the essential contract. It omits usage guidance and edge-case behavior, but those are less critical given the tool's simplicity and the existence of an output schema.

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 0% and the 'coluna' property has only a type/title, so the description carries the semantic weight. It clarifies that the parameter is the target column for an exact, case-insensitive search. An example or note about whether wildcards are accepted would strengthen it, but the core meaning is conveyed.

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 states a specific action ('Busca') and a clear resource ('uma coluna'), with an 'exata' qualifier that defines exact-match behavior. It is easy to distinguish from the table-level siblings (listar_tabelas, buscar_tabelas, descrever_tabela) even though it does not name them explicitly.

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?

No guidance is given for when to use this tool versus alternatives. The exact/case-insensitive wording implies a lookup use case, but there are no explicit when-to-use conditions, exclusions, or references to sibling tools.

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