list_intake_work_items

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

Annotations already declare readOnlyHint=true, so the agent knows it's a safe read operation. The description adds no further behavioral traits beyond the parameter list, but the read-only nature is consistent.

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 structured with Args and Returns sections, but it includes 'workspace_slug' which is not in the schema, wasting space and potentially misleading. The description is otherwise reasonably concise.

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 that an output schema exists, the description does not need to explain return values. However, the inconsistency with 'workspace_slug' and lack of pagination or filtering details beyond 'params' makes the description incomplete for a list tool. More guidance on when to use this over list_work_items would be beneficial.

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 description adds meaning by mentioning 'workspace_slug' as an argument, but this parameter is not present in the input schema, causing inconsistency. The description of 'params' as optional query parameters (per_page, cursor) adds some value, but the schema coverage is 0% and the extra invalid parameter reduces reliability.

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 'List all intake work items in a project,' which is a specific verb+resource+scope. It distinguishes itself from sibling tools like list_work_items by specifying 'intake' work items.

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 implies usage for listing intake work items in a project, but does not explicitly state when to use this tool versus alternatives like list_work_items, nor does it provide any exclusions or prerequisites.

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