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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds scope context ('private general tasks', 'selected SparkLaunch project') but does not disclose additional behavior such as pagination behavior or return format. This is acceptable given the annotations, but no extra behavioral depth is provided.

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, front-loaded sentence with no wasted words. It communicates the operation, scope, and non-mutating nature clearly and efficiently.

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 list tool with an output schema and read-only annotations, the description covers the essential scope. It does not explain limit/offset/status filtering behavior in prose, but the schema provides enough structural information for an agent. A bit more parameter guidance would make it fully complete.

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 needs to compensate. It only implies project_id via 'selected SparkLaunch project' and says nothing about limit, offset, or status. The parameter names and schema defaults provide some self-evident meaning, but the description does not add value beyond the schema for most parameters.

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 ('List'), a clear resource ('private general tasks'), and a scope ('selected SparkLaunch project'). It also explicitly notes the operation does not change anything, which distinguishes it from mutating task siblings like tasks.create, tasks.update, and tasks.delete.

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 phrase 'without changing them' clearly signals this is the read-only retrieval tool, implying use when the agent needs to view tasks rather than modify them. It does not explicitly name alternatives, but the read-only framing provides clear context.

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