cliente_favoritos

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

No annotations provided and the description fails to disclose any behavioral traits such as side effects, authentication needs, or rate limits. The single phrase offers no transparency.

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 extremely short (3 words), but this is under-specification rather than effective conciseness. It lacks essential context, making it insufficient.

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?

Given the tool's simplicity (1 param, no output schema), the description should at least state what is returned (e.g., list of favorite properties). It fails to provide complete context for an AI agent to use it correctly.

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?

The only parameter 'codigo' has no description in the schema (0% coverage) and the tool description does not explain its meaning or usage. The description adds no value beyond the schema.

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 'Imóveis favoritados' suggests this tool deals with favorited properties, but it lacks a verb indicating the action (e.g., list, get, add). The name 'cliente_favoritos' implies client favorites, so the purpose is partially clear but ambiguous.

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 on when to use this tool versus siblings like 'imoveis_listas' or 'imoveis_pesquisar'. The description does not specify context or exclusions.

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