Editar Fase Específica de uma Tarefa (executor, esforço, datas)

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

Annotations indicate destructiveHint=true and idempotentHint=true. The description confirms it modifies data, adds a warning to confirm with user, and specifies that it can change executor, dates, effort for any phase. No contradiction with 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 well-structured: a clear one-sentence summary, a use-case example, a numbered recommended flow, and a bullet list of optional fields. Every sentence adds value with no redundancy.

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 has 7 parameters (2 required) and no output schema, the description covers purpose, preconditions (list phases first), and parameter roles. It does not explain the return value or error handling, but the annotations adequately convey mutability and safety considerations.

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%, but the description adds extra context: clarifies that project_id is needed only for project tasks, groups fields as optional, and reinforces the need to use ekyte_list_task_flow_phases to get phase_id. This adds 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 uses a specific verb ('Atualiza') and resource ('fase específica dentro de uma tarefa'), and distinguishes from siblings like ekyte_toggle_flow_phase by clarifying it can update ANY phase, not just the current one.

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?

Provides a recommended two-step flow: first list phases to get phase_id, then update. Also notes that at least one optional field is required. Explicitly says to confirm changes with user. Does not explicitly state when not to use this tool versus alternatives, but the flow provides clear context.

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