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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals a critical constraint (rejection if the demand is already in another sprint), which is valuable. However, it does not mention other side effects, permissions, or success/failure response details, leaving gaps for a mutation tool.

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?

Two concise sentences front-load the purpose and key constraint with no filler or redundant phrasing. Every word contributes to the meaning, making it highly efficient.

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 association tool with two parameters and no output schema, the description covers the essential purpose and a critical rejection rule. It lacks details on return values or error codes, but the functionality is straightforward, and the description is sufficiently complete for an agent to call 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 input schema already provides descriptions for both parameters (sprint_id and demanda_id) with 100% coverage. The description adds no extra semantic detail beyond the schema, so it meets the baseline for high coverage but does not enrich parameter understanding.

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 function: associating an existing demand to a sprint, using a specific verb (Associa) and a specific resource pair (demanda, sprint). It is distinct from all sibling tools, which operate on creating demands, listing sprints, etc., making the purpose unambiguous.

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 implies its usage (associate a demand to a sprint) but does not explicitly compare it to alternatives or state when not to use it. Siblings like criar_demanda or listar_sprints are not referenced, so an agent receives no explicit guidance on selecting this tool over others.

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?

Não há annotations, então a descrição precisa carregar o peso de explicar o comportamento da operação. 'Atualiza campos de uma demanda existente' comunica mutação, mas não informa se a atualização é parcial, quais efeitos colaterais existem, se requer permissões especiais ou o que é retornado. Esse nível de detalhe é insuficiente para uma ferramenta de escrita com 16 parâmetros.

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 descrição é uma frase única, direta e front-loaded com a ação principal. O parênteses funciona como um overview útil sem repetir o schema inteiro. Não há desperdício de palavras.

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?

Para uma ferramenta com 16 parâmetros e sem saída schema, a descrição é funcional mas não completa: não diz se a atualização é parcial, como a API responde após a atualização, nem se há validações especiais entre campos como status e datas. O schema cobre os parâmetros, mas o contexto comportamental geral fica em aberto.

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?

O schema já cobre 100% dos parâmetros com descrições individuais, então a linha de base é 3. A descrição apenas resume os campos no parênteses, sem adicionar significado novo como relações entre parâmetros ou exemplos de formatação.

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?

A descrição usa o verbo específico 'Atualiza' com o recurso claro 'demanda existente' e ainda lista os campos editáveis, o que permite distinguir imediatamente de criar_demanda ou atualizar_subtarefa. Não há ambiguidade sobre a operação realizada.

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?

A expressão 'demanda existente' deixa claro que o uso é para atualização e não para criação, diferenciando-a de criar_demanda. Porém, não há exclusões explícitas ou orientação sobre quando preferir outras ferramentas, como atualizar_subtarefa.

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?

Não há annotations, então a descrição deveria cobrir mais do comportamento. Ela indica que é uma operação de mutação, mas não explica efeitos de atualização em lote, falhas parciais, permissões necessárias ou se a operação substitui preserva campos não informados.

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 frase é compacta e informativa, listando os campos alteráveis e o modo lote sem conteúdo irrelevante. É um pouco redundante ao repetir 'subtarefa', mas ainda está bem estruturada.

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?

Para uma operação de mutação sem annotations e sem output schema, a descrição é suficiente para indicar o que atualiza, mas não diz qual resposta esperar, nem alerta que nenhum parâmetro é obrigatório no schema e que um ID precisa estar presente na prática.

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?

A cobertura do schema é 100%, portanto os nomes e descrições dos parâmetros já fornecem o significado dos campos. A descrição da tool apenas repete os campos e o suporte a lote, sem resolver a ambiguidade entre 'subtarefa_id' e 'subtarefa_ids'.

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?

A descrição usa um verbo específico (atualizar), nomeia o recurso (subtarefa) e enumera os campos alteráveis, além de indicar suporte a lote. Ela é clara, mas não diferencia explicitamente a sobreposição com a sibling 'concluir_subtarefas', que também pode mudar status.

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?

A descrição informa o que o tool faz, mas não diz quando usá-lo em vez de alternativas, nem menciona pré-requisitos ou cenários apropriados. Não há orientação sobre quando preferir 'concluir_subtarefas' para alterar status para 'concluida'.

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, the description carries the full transparency burden and does disclose the core mutating behavior (changing statuses) and the bulk selection logic. But it does not clarify what happens with invalid/non-existent IDs, whether passing both selectors causes an error, or whether the operation is atomic; these gaps are representative of a mutation operation with zero annotation support.

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, front-loaded sentence captures the action and the two invocation modes without redundant text or filler. It is efficiently structured and easy to scan, earning full-conciseness score.

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?

The description covers the main invocation modes and is adequate for a simple batch-update tool, but it leaves ambiguity about whether at least one of `subtarefa_ids` or `demanda_id` is mandatory: both appear optional in the schema while the wording only implies them as alternatives. With no output schema and no annotations, a slightly more explicit note about required combinations or error behavior would complete the picture.

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 coverage is 100%, and each property already has a clear description. The tool description restates the relationship between `subtarefa_ids` and `demanda_id` but adding no richer semantics than the schema. The baseline of 3 applies because the schema does the heavy lifting.

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 opens with a concrete action ('Conclui ou altera o status') on a cleared resource ('múltiplas subtarefas') and emphasizes the batch/single-operation nature, which sets it apart from singular siblings like atualizar_subtarefa and criar_subtarefa. The tool's differentiated purpose is immediately understandable.

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 phrase 'em uma única operação' clearly signals when to use this tool over per-item updates, and the parenthesis explains the two main invocation styles (list of IDs or a demanda_id). However, it does not explicitly mention alternatives or state when not to use it, so it stops short of full explicit guidance.

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?

Não há annotations, então a descrição precisa transmitir o comportamento. Ela informa aspectos importantes: bloqueio para projetos não identificados e fila local quando a rede está offline. Porém, não fala sobre resposta/retorno, efeitos colaterais, autenticação ou o que acontece após a criação bem-sucedida.

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?

Resumo em duas frases objetivas e informativas. A primeira define o verbo e o recurso, e a segunda faz adiciona restrições e comportamento específico sem desperdício. Cada frase agrega valor.

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?

Para uma operação com 15 parâmetros e sem output schema, a descrição fornece as regras essenciais de comportamento, mas omite o que é retornado ao cliente e alguns cenários de erro além do projeto não identificado. Seria mais completo se descrevesse o retorno ou detalhes de criação bem-sucedida.

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?

O schema possui cobertura de 100%: todos os 15 parâmetros têm descrições. A descrição da ferramenta não adiciona semântica de parâmetros além do schema, o que define o baseline adequado de nota 3.

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?

O verbo 'Registra' com o objeto 'nova demanda' e o contexto 'sistema de Gestão de Tarefas' delimitam claramente o propósito de criação de uma demanda. Apesar de não citar explicitamente os irmãos (como criar_subtarefa ou atualizar_demanda), a descrição é específica o suficiente para diferenciar a operação.

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?

A descrição indica condições de uso relevantes: a operação é bloqueada para projetos não identificados ou ignorados e, offline, salva na fila local. Contudo, não menciona alternativas (ex.: usar atualizar_demanda para demandas já existentes) nem exclui explicitamente cenários, deixando parte do contexto de uso implícito.

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 behavioral disclosure burden. It does a good job by revealing that the operation can be blocked for unqualified projects and that offline calls are stored in a local queue for later submission. It does not mention auth requirements or result handling, but the core behavioral traits are disclosed.

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 three well-structured sentences, each delivering a distinct piece of information: what the tool does, when it is blocked, and how offline behavior works. There is no filler or unnecessary repetition.

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 absence of annotations and output schema, the description gives essential context about offline behavior and blocking, which improves call accuracy. It could additionally clarify what the agent receives after submission, especially in offline mode, but the current description still covers the main operational context.

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%, so the input schema already documents all six parameters. The tool description adds no additional parameter-level meaning beyond what the schema provides, which meets the baseline but does not go further.

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 ('Cria') and clearly defines the resource as a technical subtask linked to an existing demand. This differentiates it from sibling tools like criar_demanda, atualizar_subtarefa, and concluir_subtarefas without requiring the agent to inspect schemas.

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 text establishes that the subtask must be tied to an existing demand ('demanda existente'), making it clear this is not for new demands, and it describes blocking conditions for unidentified/ignored projects. It does not explicitly name alternative sibling tools, but the demand-vs-subtask distinction is evident.

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 disclosing behavior. It says 'lista' (lists) but does not explicitly state whether it's read-only, whether it filters by default (only open/in-progress) or returns all statuses when no filter is applied, or any pagination/sorting behavior. The mismatch between the description's 'abertas ou em andamento' and the schema's full status enum adds ambiguity.

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 sentence that conveys the core purpose and a contextual use case without any filler. It is concise and front-loaded with the main action.

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 that there is no output schema and no annotations, the description should provide more context about what the tool returns (e.g., list of demand objects, key fields) and any default behavior. The description mentions a use case but does not explain the response format, filtering defaults, or relationship to subtask linking. It is under-specified for a tool with 3 parameters and no structured output.

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 coverage is 100% with all three parameters (projeto_id, status, responsavel_id) having descriptions. The tool description adds no additional meaning beyond the schema, so it meets the baseline of 3 but does not exceed it.

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 it lists demands (verb+resource) for a project. It distinguishes itself from siblings like listar_projetos and obter_detalhes_demanda by focusing on the collection of demands. However, the phrase 'abertas ou em andamento' is slightly misleading since the schema's status enum includes all statuses (e.g., concluida, cancelada), so the description under-specifies the actual scope.

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 mentions a use case (análise de contexto e vínculo de subtarefas), which implies when to use it, but it does not explicitly state when NOT to use it or compare with alternative tools like obter_detalhes_demanda or obter_contexto_projeto. The guidance is implicit, not explicit.

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, the description must disclose behavior, but it is sparse. It claims to list 'all projects' while the schema has a status filter with a default of 'ativo', which contradicts the 'todos' wording—potentially misleading an agent about the default scope. It also fails to mention any side effects, permissions, pagination, or response format, which are critical for a tool without annotations.

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 with no redundant words or filler. It front-loads the action and resource, making it easy to parse. Every word earns its place, and there is no bloat.

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 listing tool with an optional parameter and no output schema, the description is minimally functional but leaves gaps. The mismatch between 'todos' and the default 'ativo' filter is a notable incompleteness, and there is no guidance on expected output or pagination. While the simplicity reduces the burden, the description could benefit from clarifying the default behavior and any restrictions.

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 schema already fully describes the single parameter (status) with 100% coverage, giving the agent sufficient detail on filtering. The description adds no further semantic value, but since the schema covers it, the baseline of 3 is appropriate. However, it does not clarify the interaction between 'todos' and the default filter value.

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 action (listing projects) and the resource (projects in the Task Management system). It uses a specific verb and resource, making the primary purpose unambiguous. However, it does not explicitly distinguish this tool from sibling tools like 'listar_demandas_ativas' or 'listar_sprints', though the resource type is distinct enough that confusion is unlikely.

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. It does not mention prerequisites, context, or exclusions (e.g., when to use 'obter_contexto_projeto' instead). No comparison with sibling tools is made, leaving the agent without direction on selection.

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, the description carries the behavioral burden. It discloses the visibility filter and sorting order, which are non-obvious behavioral details. It does not explicitly state that this is a read-only operation, but the verb 'Lista' strongly implies it.

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, front-loaded sentence that conveys the action, resource, scope, and order without any filler. Every word 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?

For a zero-parameter, read-only listing tool with no output schema, this description is complete: it states what is listed, which items are included, and how they are ordered. No additional context is necessary for selection or 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?

The tool has 0 parameters, so the schema provides complete coverage and there is nothing for the description to add. The baseline of 4 applies because the description does not need to explain parameter semantics.

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 ('Lista') and resource ('sprints'), adds a meaningful scope ('visíveis'), and specifies ordering ('da mais recente para a mais antiga'). This clearly distinguishes it from sibling tools like listar_projetos and listar_demandas_ativas.

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 purpose implies use when listing sprints, and the ordering/visibility details add context, but the description does not explicitly state when to prefer this tool over alternatives or provide any exclusions. It relies on the tool's name and obvious purpose.

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 must carry the behavioral burden. It discloses the detection mechanism, indicates it is a discovery/identification operation, and describes the stateful disabled condition. A more explicit statement that the operation does not mutate anything and does not require special authentication would make it fully transparent.

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 sentence that front-loads the main purpose. Every phrase adds meaningful detail: the method, the current directory basis, and the disabled condition. There is no redundancy or filler.

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 tool with one optional parameter and no output schema, the description is mostly complete: it explains the input context, the source of project detection, and the potential disabled state. It could briefly state the shape of the returned value or the explicit outcome enum, but the absence is a minor gap.

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 input schema fully describes 'diretorio_path' with its default behavior. The description adds no additional parameter-specific details, either in the rest of the schema or in the description, so the baseline of 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 action and resource: it identifies the active project based on the current working directory. It also conveys the prediction behavior and makes it easy to distinguish from sibling tools like 'listar_demandas_ativas' or 'criar_demanda', since this one is about context/discovery, not listing or mutation.

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 of when to use this tool: when the active project context is needed, determined from the current directory. It also mentions the disabling condition for external or unidentified projects, which functions as a when-not signal. It does not explicitly point to a direct sibling alternative, preventing a perfect score.

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. It mentions inclusive details (subtarefas e responsáveis) but does not disclose any behavioral traits such as read-only nature, performance, or side effects. For a read-like operation, it lacks explicit safety confirmation.

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?

Single sentence, clear and front-loaded with the purpose. No wasted words, though it could arguably mention alternatives for conciseness's sake.

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?

Tool is moderately simple (1 parameter, no output schema). Description covers the purpose and inclusion of subtasks, but without annotations or additional behavioral info, completeness is adequate but not rich. No mention of return format or error conditions, but simple enough.

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%, so the schema already explains the 'demanda_id' parameter. The description repeats that it consults a specific demand but adds no extra semantic detail beyond what the schema provides. Baseline of 3 applies.

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 that the tool retrieves full details of a specific demand, including subtasks and those responsible. It uses a specific verb ('consulta') and resource ('demanda específica'), and distinguishes from siblings like 'listar_demandas_ativas' by focusing on a single item.

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 implies usage for viewing details of one demand, but does not explicitly state when to use it versus alternatives like 'listar_demandas_ativas' (for listing) or 'obter_contexto_projeto' (for project context). No exclusions or alternatives are mentioned.

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 present, so the description carries the full burden of behavioral disclosure. It reveals that credentials can come from saved storage or from provided parameters, but it fails to mention side effects such as invalidating the current session, what happens if no saved credentials exist, or how failures are reported.

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 sentence that front-loads the action and explains the credential source in a compact, readable way. There is no filler or 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?

This is a fairly simple tool with only two optional parameters, and the description captures the essential operation. However, since there is no output schema and no annotation coverage, the description could have mentioned observable behavior, such as silent renewal, session invalidation, or authentication error behavior, to be fully self-contained.

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%, so the schema already documents email and password as optional if credentials are locally configured. The description adds little semantic value beyond restating that saved or new credentials are used, so the 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 clearly states a specific action: renew the authentication session for the Gestão de Tarefas system, using either saved or provided credentials. Although it does not explicitly differentiate itself from sibling tools like verificar_status_conexao, the action and resource are uniquely identifiable.

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?

There is no guidance on when to use this tool versus alternatives such as verificar_status_conexao, nor any mention of prerequisites or exclusions. The description only implies that renewal is the intended purpose, so an agent gets no help choosing it over related authentication/connection tools.

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, the description carries full responsibility. It discloses that the tool forces sending of all offline items, but omits critical details: what happens to local copies after sync, whether the operation is blocking or asynchronous, failure handling, or if it clears the queue. The impact of this mutation is not clarified.

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, concise sentence that efficiently communicates the action and scope. It is front-loaded with the verb and resource, has no fluff, and every word contributes meaning.

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 (no params, no output schema), the description is mostly adequate but has gaps: it does not address edge cases like network failures, duplication of sends, or the effect on local data after successful sync. These are relevant for a mutation tool and would improve completeness.

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 tool has zero parameters, so the schema covers everything. The description adds no parameter information, but that is unnecessary. According to the baseline for 0-parameter tools, a 4 is appropriate; no compensation is required.

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 verb ('Força o envio') and resource ('todas as demandas e subtarefas'), specifying their origin (generated locally while offline). It distinguishes this from sibling tools like criar_demanda or listar_demandas_ativas by focusing on the sync action, though it doesn't explicitly name alternatives.

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 implies the intended use case (syncing offline-generated items after reconnection), but does not explicitly state when to use it versus other tools, nor provide exclusions or prerequisites like checking connection status via verificar_status_conexao. Guidance is implicit from the context.

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?

Sem anotações, a descrição carrega o ônus de explicar o comportamento. Ela indica que é uma operação de leitura ('Informa'), mas não declara explicitamente que não modifica dados nem tem efeitos colaterais. Para uma ferramenta de status, é aceitável, mas poderia reforçar a ausência de mutação. Não contradiz o esquema.

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?

Uma única frase, direta e sem excessos, lista os três itens de saída principais. Carga informativa alta com zero desperdício.

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?

A descrição cobre os três aspectos do status (conexão, token, fila offline). Sem saída estruturada e sem anotações, essa é uma informação suficiente para um tool de verificação simples. Faltaria apenas uma menção explícita a ser read-only para completar totalmente o contexto.

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?

A ferramenta não possui parâmetros, então a cobertura do esquema é 100% trivial. A descrição não precisa explicar parâmetros inexistentes. Pontuação base para 0 parâmetros é 4.

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?

A descrição informa claramente a finalidade: reportar estado da conexão, validade do token e quantidade de itens na fila offline. O verbo 'Informa' e o recurso específico (estado da conexão, token, fila) diferenciam de todos os irmãos, que tratam de projetos, demandas, sprints e sincronização.

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?

Não há orientação explícita sobre quando usar esta ferramenta em relação às alternativas. A descrição não menciona, por exemplo, que deve ser chamada antes de sincronizar a fila offline ou para diagnosticar falhas de conexão. Apenas descreve o que faz, sem contexto de uso.

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