get_task_statuses

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

No annotations provided, so the description carries behavioral burden. It discloses the default session behavior but does not mention read-only nature, permissions, or other traits. Adequate for a simple list operation.

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-loaded with purpose and a usage hint. No unnecessary words.

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?

With an output schema, return format is likely clear. Description covers session behavior but missing details on whether statuses are project-specific or custom. Sufficient for a simple list tool.

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 0%, so description must explain parameters. It adds context for session_id (default session) but does not describe project_id format or constraints. Some value beyond schema names.

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 'Lists' and the resource 'available statuses for tasks within a specific project', distinguishing it from sibling tools like get_issue_statuses and get_user_story_statuses by specifying tasks.

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 notes that a default session is used if session_id is not provided, offering guidance on optional parameter usage. No explicit when-not or alternatives, but context implies usage for task statuses.

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