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

Annotations already declare readOnlyHint=true, and the description repeats 'Read-only,' so the safety profile is covered. The description adds value by specifying the return contents (drawing task, reference photo URL, submission limits), but it does not disclose any additional behavioral traits such as potential errors, auth requirements, or response format. Since annotations carry the read-only burden, this is adequate.

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 the key verb and resource list. Every word earns its place, and it is immediately clear what the tool does without any fluff.

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 read-only getter with no parameters and no output schema, the description covers the essential return items. It does not specify the exact data structure or error handling, but that is not critical given the tool's simplicity. The annotations cover safety, and the description provides sufficient context for an agent to call it 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?

The tool has zero parameters, so the schema has 100% coverage vacuously. According to the guidelines, the baseline is 4. The description correctly omits parameter details since none exist, so there is nothing to compensate for.

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 clearly states the specific verb 'Returns' and the resource: the drawing task, reference photo URL, and submission limits. This is distinct from the sibling tools check_drawing and submit_drawing, which imply different actions (checking vs. submitting). The title 'Read the task' reinforces the purpose.

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 does not explicitly mention when to use this tool over alternatives. However, the read-only nature and the content (task info) imply it's for fetching task details before drawing or checking, but no exclusions or explicit routing are provided. The usage context is clear but not elaborated.

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