get_flagged_tasks

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

The description implies a read operation but provides no additional behavioral details. With no annotations, it fails to disclose potential side effects, rate limits, or data limitations, such as whether pagination or sorting is supported.

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 at one sentence, but its brevity sacrifices clarity. It is appropriately sized for a simple tool but could benefit from more context.

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 lack of annotations, output schema, and parameter details, the description is incomplete. It does not explain what constitutes a 'flagged' task, how results are ordered, or if there are any limits on the number of tasks returned.

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 schema has zero parameters and 100% coverage, so the description does not need to explain parameters. However, it adds minimal semantic value beyond the tool name by stating 'all available' flagged tasks.

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 tool retrieves 'flagged tasks', which is distinct from sibling tools like 'list_tasks' or 'get_inbox_tasks'. However, it does not specify what 'flagged' means or if there are any filtering criteria.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention use cases, prerequisites, or situations where another tool would be more appropriate.

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