books_get_items

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

Although annotations include readOnlyHint and idempotentHint, the description adds valuable context beyond those: prerequisites (inventory management permissions), error recovery guidance (verify setup and permissions), and scope clarification (includes products and services). It does not contradict any 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 well-structured with clear sections (Prerequisites, Next Steps, Workflow, Error Recovery). Every sentence serves a purpose, and the most important information (what it does and why it's essential) is front-loaded. It is concise yet comprehensive.

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?

The description covers usage workflow, prerequisites, and error recovery, but lacks explicit details about the return format and pagination behavior. It only hints that item_id and details are available for invoice line items. Given the absence of an output schema, more explanation of response structure would improve completeness, but the description is adequate for a list-oriented read-only tool.

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 description does not mention any of the 6 parameters (page, per_page, filter_by, sort_order, search_text, sort_column). Schema description coverage is 0%, and the description provides no guidance on how to use filtering, sorting, or pagination, leaving the agent to infer from generic names.

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 tool's function: 'Get all items from Books including products and services available for billing.' It distinguishes itself from the sibling tool books_get_item by noting it returns all items for billing, and explicitly recommends books_get_item for detailed item information.

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 provides strong usage context by calling the tool 'ESSENTIAL for invoice line items' and outlines a complete workflow (books_get_items → books_create_invoice → books_create_payment). The 'Next Steps' section explicitly directs when to use sibling tools like books_get_item and books_create_item, offering clear alternatives and sequencing.

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