buscar_projetos

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

No annotations are provided, so the description carries full behavioral disclosure burden. 'Busca' implies a read-only search, but the description does not state whether results are paginated, what permissions are required, or any side effects, leaving a significant gap for a tool with zero annotation coverage.

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 a single, front-loaded sentence with no wasted words. It is appropriately brief for a simple search tool, though its extreme terseness leaves some contextual gaps.

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 one-parameter search tool with 100% schema coverage and no annotations, the description covers the core action and criteria. However, without an output schema or annotation hints, it does not describe return values or behavioral traits, leaving the definition adequate but incomplete.

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 100%, and the single parameter 'termo' is already fully documented in the schema. The description merely restates the same search scope ('nome ou tecnologia') without adding syntax, format, or matching behavior details, so baseline 3 is appropriate.

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 verb ('Busca') and resource ('projetos') with its scope ('por nome ou tecnologia'). It is clearly distinguishable from sibling tools like buscar_experiencias because the resource differs, though it does not explicitly name an alternative to avoid confusion.

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 search criteria ('por nome ou tecnologia') imply when to use the tool, but there is no explicit guidance on when to choose it over siblings like buscar_experiencias or listar_habilidades, nor any exclusions.

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