get_checkitem

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

No annotations are provided, so the description must carry the transparency burden. It only says 'get,' implying a read-only operation, but it does not disclose return format, behavior when the checkitem is not found, authentication needs, or any side effects. For a simple read tool, this is minimal but still a gap.

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?

Two sentences, but the second ('Use this tool to get details about a particular checkitem') largely repeats the first. It is short but contains redundancy. A single sentence would be more concise.

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 'get by ID' operation, the description is acceptable but not complete. There is no output schema, so the description does not clarify what details are returned or how detailLevel influences the response. It relies on the schema for parameter information and does not explain the relationship between checklistId and checkItemId.

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% with all parameters described. The description adds no additional meaning beyond the schema, such as how to obtain the IDs or how fields/detailLevel affect the response. Baseline 3 is appropriate when schema does the heavy lifting.

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 uses a specific verb-resource combination: 'Get a specific checkitem on a checklist.' This distinguishes the tool from siblings like get_checkitems (which lists all) and other checkitem operations. However, it does not explicitly name alternatives, so it's clear but not fully differentiated.

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 says 'Use this tool to get details about a particular checkitem,' which provides basic context. But it does not state when not to use it or compare it to get_checkitems, create_checkitem, etc. Guidance is implied rather than explicit.

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