get_my_current_tasks

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

The description discloses that it returns slim work items and aggregated statistics, and explains auto-fetch vs. manual pagination. However, with no annotations, it fails to cover other behavioral aspects such as authentication requirements, rate limits, or the impact of querying all items.

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 concise (three sentences), front-loaded with the main action, and each sentence provides unique, valuable information. 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?

Given the absence of an output schema, the description appropriately explains the return format (slim work items with aggregated stats) and pagination behavior. It could mention error conditions or performance implications, but it covers the essential aspects for a tool with good schema coverage.

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%, so baseline is 3. The description adds value by explaining the auto-fetch versus manual pagination modes for limit and offset, and clarifying that omitting limit/offset triggers auto-fetch of all items. This goes beyond the schema descriptions.

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 it gets the current user's assigned tasks with aggregated statistics, and mentions slim work items and pagination modes. However, it does not explicitly differentiate from sibling tools like 'get_my_tasks' or 'get_incomplete_tasks', which may perform similar functions.

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 information about pagination modes but gives no guidance on when to use this tool versus alternatives (e.g., get_my_tasks, get_incomplete_tasks). There is no mention of prerequisites or 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.