task_flags

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

With no annotations, the description carries the full burden; it does disclose what categories of results come back, which is real behavioral content, and the word 'view' weakly implies read-only. It omits whether the result set is OR-combined across flags, whether there is a limit or ordering, and never states that the call is non-mutating.

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?

A single front-loaded sentence that enumerates the flags without filler; the condition list is dense but every item earns its place. It could be marginally tighter by folding the hour-window mention into the flags list.

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?

There is no output schema, so the flag enumeration usefully stands in for describing return categories, but for a two-parameter aggregation view with zero annotation coverage the definition should still state read-only behavior, result ordering/limits, and the meaning of the stale threshold.

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 0%, so the description must compensate. 'Tasks created in the last N hours' directly explains created_within_hours, and the 'stale' flag plus the stale_hours name together imply a staleness threshold, but neither default (24) nor how staleness is measured is clarified.

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 names a concrete result set ('check-in view') and enumerates the exact conditions surfaced: overdue, stale, blocked, waiting_on_owner, owner questions, and recently created tasks. That is specific enough to separate it from generic listing siblings, though it never uses an explicit verb (list/return) and does not mention the overlapping sibling task_stale.

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?

Usage is only implied by the label 'Check-in view', which suggests a periodic health sweep rather than a general query. There is no explicit statement of when to prefer this over task_list or task_stale, even though task_stale clearly overlaps with the 'stale' category here.

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