get-project-tasks-by-phase

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

With no annotations, the description should describe behavioral traits like read-only nature, error handling, or pagination. It only states 'get all project tasks' without mentioning that it is safe/read-only or any side effects. The agent cannot anticipate what happens with invalid phase_id or performance implications.

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, precise sentence. No redundant words or unnecessary details. It conveys the essential purpose efficiently.

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 number of sibling tools and the lack of output schema, the description is too minimal. It does not explain return format, ordering, default values for optional parameters, or behavior when no tasks exist. An agent would need to guess details that could affect tool selection.

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%, so the schema already describes each parameter. The description adds no extra meaning beyond 'for a specific project phase', which is already implied by the tool name. It does not provide examples or constraints beyond the schema, but baseline 3 is appropriate given high schema coverage.

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 (Get), resource (all project tasks), and filter (for a specific project phase). Unlike ambiguous names, this description makes it easy for an agent to distinguish from siblings like get-project-tasks-by-project.

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 is provided on when to use this tool versus alternatives such as get-project-task, list-project-tasks, or get-phases-by-date-range. The agent is left to infer appropriate usage without any contextual hints.

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