task_list

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

No annotations provided; description discloses the source file and return type (string of tasks) but lacks details on side effects, error handling, or behavior beyond reading a file.

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?

Concise: two sentences plus structured Args/Returns section. No redundant information, every part serves a purpose.

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 (one required parameter, no output schema, no nested objects), the description adequately covers purpose, input, and output format. Could mention output format in more detail.

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 has 0% coverage; description adds meaning by specifying that the parameter is the project path derived from user_info, beyond just the schema title 'Current Project'.

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?

Clearly states 'List all tasks defined in the current project's Taskfile.yml', identifying the specific verb and resource, and differentiating from sibling tool 'run_task'.

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 usage context: 'The caller should look for their current project in user_info and pass the project path to this tool.' This guides the agent on sourcing the input, though it doesn't extensively discuss when not to use it.

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