get_task_notes

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

No annotations are provided, so the description must carry the burden. 'Get' implies a read-only operation, but the description does not disclose potential behaviors such as whether resolved notes are included, ordering, or pagination. It is minimally transparent but not misleading.

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 a single concise sentence with no unnecessary words. It is front-loaded with the action and resource, making it quickly parsable.

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?

For a simple single-parameter getter, the description is nearly complete. It does not explain the return format or note statuses, which could be ambiguous given sibling tools for resolving/escalating notes, but the low complexity keeps the gap small. An output schema is absent, so a bit more detail would help, but it is still sufficient for selection and invocation.

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% (task_id is described as 'Task ID'), so the baseline is 3. The description does not add any extra meaning beyond the schema parameter. It neither enriches nor repeats the parameter explanation, which is acceptable for a single obvious parameter.

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 'Get all working notes for a task' uses a specific verb ('get'), a specific resource ('working notes'), and a scope ('for a task'). It clearly distinguishes from sibling tools like add_working_note, resolve_working_note, and escalate_working_note by being the retrieval operation.

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 implies usage: one would call this when they need all working notes for a task. However, it provides no explicit context, exclusions, or alternatives. The usage is evident from the purpose, but there is no guidance on when not to use it or how it differs from get_task_details.

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