Get items in a list

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

Discloses default exclusion of completed items and return format. But no annotations present, and description omits other behavioral traits such as read-only nature, pagination, ordering, or error handling.

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?

Three concise sentences with front-loaded purpose. No extraneous information, every sentence adds value.

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?

Simple tool with only two parameters; description covers default behavior and output structure. Missing potential details on ordering or limits, but sufficient for basic usage.

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%, but description indirectly explains include_completed via 'excludes completed items by default'. Does not elaborate on list_id format or constraints beyond implying it identifies a list.

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?

Description states 'Items in one list' and provides return format, clearly indicating it retrieves items from a specific list. Distinguishes from sibling tools like get_lists (returns lists) and mutation tools like add_item.

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?

No explicit guidance on when to use this tool versus alternatives. Implied by context, but no direct mention of exclusions or comparisons to siblings like update_item or remove_items.

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