get_my_tasks

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

No annotations are provided, so the description carries the full burden. It states the tool is read-only (returns items), but does not disclose any side effects, authorization needs, rate limits, or behavioral constraints. The mention of a return structure is helpful but minimal.

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 two sentences with zero unnecessary words. The main action is front-loaded, making it immediately clear what the tool does.

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?

While the description covers the basic purpose and return format, it lacks details on pagination, parameter interactions, or the fields within each item. Given no output schema, more context would be beneficial for a complete understanding.

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 100%, and the tool description does not add extra meaning beyond the schema's parameter descriptions. The description merely lists the action and return shape without elaborating on how parameters affect behavior.

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 'Get work items assigned to the current user', specifying both the action (retrieve) and the resource (tasks of the current user). It also mentions the return structure '{ items, total }'. This distinguishes it from siblings like 'list_work_items' (which likely returns all work items) and 'get_my_current_tasks' (which may filter by active status).

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 provides no guidance on when to use this tool versus alternatives like 'search_work_items' or 'get_incomplete_tasks'. It lacks explicit conditions, exclusions, or references to sibling tools, leaving the agent without context for optimal selection.

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