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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the external API (ViaCEP) which adds some context, but doesn't describe error handling, rate limits, authentication requirements, or what happens with invalid CEP formats beyond the two examples given. For a tool that queries external data, this is a significant gap.

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 efficiently structured with clear sections: purpose statement, Args with parameter details, and Returns with output information. Every sentence adds value without redundancy, making it easy to parse and understand quickly.

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 single-parameter lookup tool with no output schema, the description provides adequate coverage of the basic functionality. It explains what the tool does, parameter format, and return structure. However, it lacks important contextual details like error conditions, API limitations, or performance characteristics that would be helpful for an AI agent.

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 description provides valuable parameter semantics that aren't in the schema. While the schema only indicates 'cep' is a required string, the description specifies it must be a Brazilian postal code and shows two valid formats (01001000 or 01001-000). With 0% schema description coverage, this description compensates well for the single parameter.

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 clearly states the tool's purpose: 'Consulta informações de um CEP brasileiro' (consult information about a Brazilian postal code). It specifies the action (consult) and resource (CEP information), though it doesn't explicitly differentiate from its sibling 'buscar_ceps_por_logradouro' beyond the different input method.

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 provides no guidance on when to use this tool versus alternatives. While it mentions the API (ViaCEP), it doesn't indicate when to choose this over 'buscar_ceps_por_logradouro' or other potential methods for obtaining Brazilian address information.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the search functionality and return format ('Lista de dicionários com endereços'), but doesn't mention potential limitations like partial matches, empty results, rate limits, or authentication requirements. It adequately covers basic behavior but lacks operational details.

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 perfectly structured and concise. It begins with the core purpose, then provides a well-organized parameter section with clear examples, and concludes with return value information. Every sentence adds essential value with zero waste.

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 moderate complexity (3 required parameters, no output schema, no annotations), the description is quite complete. It covers purpose, parameters with examples, and return format. However, without annotations or output schema, it could benefit from more behavioral context about how the search works and what the returned dictionaries contain.

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 description provides excellent parameter semantics beyond the 0% schema coverage. It clearly explains each parameter's purpose with concrete examples: 'uf: Sigla do estado (ex: SP, RJ)', 'cidade: Nome da cidade (ex: São Paulo)', and 'logradouro: Nome da rua, avenida, praça etc (ex: Praça da Sé)'. This fully compensates for the lack of schema descriptions.

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 clearly states the tool's purpose with specific verb ('Busca') and resource ('CEPs associados a um logradouro'), including the required geographic context ('em uma cidade e estado'). It distinguishes itself from the sibling 'buscar_cep' by specifying it searches for multiple CEPs associated with a street rather than a single CEP.

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 provides clear context for when to use this tool (searching for all CEPs associated with a street in a city/state). It doesn't explicitly mention when NOT to use it or name alternatives, though the distinction from 'buscar_cep' is implied by the different functionality described.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'repeats' text, implying a read-only or echo operation, but doesn't disclose any behavioral traits such as side effects, error handling, or output format. This is a significant gap for a tool with no 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, efficient sentence in Portuguese ('Repete o texto enviado'), with zero wasted words. It's appropriately sized and front-loaded, conveying the core purpose without unnecessary elaboration.

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 low complexity (1 parameter, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks details on behavior, usage, or output. For such a simple tool, this might be adequate, but it leaves gaps in understanding how the tool operates beyond its basic function.

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 description adds no parameter semantics beyond the input schema, which has 0% description coverage. However, with only 1 parameter ('texto'), the tool's purpose inherently clarifies its use: the parameter is the text to repeat. This compensates well for the low schema coverage, making the parameter meaning clear from context.

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 'Repete o texto enviado' (Repeats the sent text) states the tool's purpose with a clear verb ('repeats') and resource ('text'), but it's somewhat vague about what 'repeats' entails (e.g., returns, outputs, echoes). It doesn't distinguish from sibling tools like 'buscar_cep', but they serve different functions, so differentiation isn't critical here.

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 provides no guidance on when to use this tool versus alternatives or in what context. It lacks explicit usage instructions, prerequisites, or exclusions, leaving the agent to infer usage based on the simple purpose alone.

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