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

With readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the safety profile is already covered. The description adds a useful behavioral fact—bulk execution via oportunidade_ids—but does not go further into response details, error behavior, or how the batch interacts with required fields.

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 only two sentences, front-loads the core purpose, and adds the batch detail without fluff. Every part 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?

With no output schema and low parameter coverage, the description leaves important gaps, including the role of `query`, how to combine `oportunidade_id` and `oportunidade_ids`, and what a batched request response may look like. It is minimally usable for the simple case but incomplete for full tool invocation.

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 description coverage is 0%, so the description must compensate. It only explains that `oportunidade_ids` enables batch execution, while the `query` parameter is completely unexplained and the required field `oportunidade_id` creates ambiguity when `oportunidade_ids` is also provided.

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-resource pair ('Busca uma oportunidade por ID') and clearly distinguishes the singular fetch operation from list/create/get sibling tools. The bulk-support note further clarifies this tool's scope beyond a simple get.

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 clearly implies the tool is for retrieving a single opportunity by ID, optionally batched. It does not explicitly state when to prefer this over list_oportunidades or how to choose between single and bulk, but its contextual use case is obvious.

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