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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description adds valuable behavioral context: thumbnail size estimates (~5-15KB each), REST endpoint behavior, nextActions context-awareness, and an explicit 'Requires authentication' note. No contradiction with annotations.

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 longer than average but well-structured with a numbered list. Every sentence serves a purpose—explaining levels, endpoints, and nextActions—so the length is justified. Not maximally concise, but efficient for the complexity.

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 there is no output schema, the description covers return contents (metadata, GPS, validation), response size implications, alternative endpoints, authentication, and nextActions behavior. It does not detail the exact JSON structure, but for a read-only get operation with this level of guidance, it is sufficiently complete for an agent to invoke correctly.

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?

With 100% schema coverage, the baseline is 3, but the description enriches parameter understanding by explaining the trade-off of includeThumbnails (lightweight vs inline base64) and suggesting REST endpoints as an alternative to avoid pulling all thumbnails. This goes beyond the schema's field descriptions.

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 opens with a precise verb+resource statement: 'Get all proof items submitted by the operator for a task.' It clearly distinguishes this from sibling tools by focusing on proof items and enumerating return types (metadata, GPS stamps, validation results), making it unique among get_task_* tools.

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?

It provides clear instructions on how to choose between default lightweight output and includeThumbnails=true, plus alternative REST endpoints for single thumbnails and raw content. It implies usage context ('when you need proofs') but doesn't explicitly name alternatives or exclusions, so a point is deducted.

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