analyze_session_for_tasks

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

No annotations exist, so the description carries the full behavioral burden. It hints at LLM processing ('Use AI'), which implies non-determinism and possible latency/cost, but it says nothing about whether tasks are created or mutated, what permissions are needed, or what the result contains. For an unannotated tool this leaves the agent guessing about side effects.

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 with no filler. It is efficiently sized, though its brevity is partly under-specification rather than tight editing.

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?

With no annotations, no output schema, and an optional-only 2-parameter schema, the description should explain what the analysis returns and whether it produces or merely reports on tasks — the name 'for_tasks' suggests possible task generation that is never clarified. The mutual exclusivity of session_id and session_notes is also left unstated.

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%, so both parameters are already documented in the schema, making 3 the baseline. The description mentions 'session context notes,' loosely echoing session_notes, but adds no guidance on the session_id vs. session_notes choice or on the fact that zero parameters are required (i.e., whether one of the two must be supplied).

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 states a specific verb (analyze), a specific resource (agent-modes session context notes), and the dimension being analyzed (task completion and progress). It is distinguishable from siblings like summarize_task_description or scan_recent_sessions by naming the agent-modes session source, though it never explicitly contrasts itself with those neighbors.

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 purpose statement — an agent can infer this is for evaluating session notes against task progress, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., vs. scan_recent_sessions or recommend_daily_tasks_ai). No prerequisites or input-selection guidance is given.

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