list_project_task_assignments

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

No annotations provided, so description carries the burden. 'Retrieve' suggests read-only operation, but no explicit statement of non-destructiveness, idempotency, or side effects. Description adds basic behavioral info but lacks safety guarantees or rate limit notes.

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 sentences, concise and front-loaded. First sentence states purpose, second adds relevant context. No extraneous 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?

No output schema or annotations. Description explains what the tool returns conceptually (task assignments with settings) but lacks details on pagination behavior, response structure, sorting, or default values. Adequate for a simple list tool but not fully complete.

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%, with descriptions for each parameter. The tool description adds context ('available for time tracking on the project and their specific settings') but does not provide additional semantic value beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'Retrieve task assignments for a specific project' and adds context about time tracking and settings. It distinguishes from sibling tools like list_tasks (which lists tasks, not assignments) and get_project (project details). Verb 'Retrieve' with resource 'task assignments for a specific project' is specific.

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 explicit guidance on when to use this tool vs alternatives. Description implies use when needing assignments for a project, but doesn't mention when not to use it or compare with siblings like create_project_task_assignment or update. Context signals show there are sibling tools for CRUD on assignments, but no differentiation.

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