Listar Fases de uma Tarefa (com Executor por Fase)

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

Annotations already declare readOnlyHint, destructiveHint false, and idempotentHint true, so the description adds context about the returned fields (phase_id, executor, dates, etc.) and the factual nature of the data. No contradictions; the description adds moderate value beyond 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 concise: two sentences for purpose, one for usage guidance, and a bulleted differentiation. No unnecessary words, and key information is front-loaded.

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 tool is simple (list operation) with robust annotations and schema. The description explains what each returned phase includes (phase_id, sequential, name, executor, effort, dates), compensating for the lack of an output schema. All necessary context is provided.

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 has 100% coverage with descriptive parameter descriptions. The description additionally mentions that task_id can be discovered via ekyte_list_tasks, adding extra guidance. Since schema coverage is high, this exceeds the baseline of 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?

The description clearly states it lists all phases of a specific task, showing executor, dates, and estimated time per phase. It explicitly distinguishes itself from the sibling tool ekyte_list_phases by contrasting template vs actual phases.

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 advises using this tool before editing a phase with ekyte_update_phase, providing clear context for when to invoke it. It also differentiates from ekyte_list_phases, offering alternative usage guidance.

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