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

Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds 'Somente dados públicos', which clarifies scope and access expectations, but does not disclose pagination behavior, ordering defaults, or return format.

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 front-loads the action and resource while efficiently listing the key filter dimensions. The phrase 'Somente dados públicos' adds meaningful scope without unnecessary detail.

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 12-parameter search tool with no output schema, the description covers the primary filter dimensions and public-data scope, making it adequate for tool selection. It does not describe return shape, defaults for pagination/sorting, or how parameters interact, leaving some invocation details to the 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 description coverage is 42%, and the description adds meaning by naming searchable dimensions like city, price range, bedrooms, and amenities, which partially compensates for undocumented parameters. However, it says nothing about pagination, sort/order semantics, or how filters combine, so it only partially bridges the 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 states a specific action ('Busca') and resource ('empreendimentos publicados na ObraAberta'), and enumerates the main filter dimensions. It does not explicitly name sibling tools, but the broad text/city/state search scope is clear.

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 gives clear context for when to use the tool: searching public projects by various criteria. It does not explicitly mention alternatives like find_projects_nearby or get_builder_projects, but it implies its role as the general public search tool without exclusions.

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