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

Beyond the readOnlyHint annotation, the description surfaces meaningful behavior: the list is the shared List It list, not the phone-only one; it returns line-level detail; it includes an `available` flag and a `note`; and it explains the `since`/`seq` mechanism for a cheap `unchanged` response. This is rich context an agent needs to handle the tool correctly.

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 information-dense and front-loaded: scope first, then usage, then a key caveat, then parameter guidance. Each sentence earns its place. It is longer than a minimal description, but the extra context (phone-only list, note, unchanged behavior) is essential for correct calling.

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 read-only tool with one optional parameter and no output schema, the description covers the returned data (lines, crossed-off states, aisles, recipe sources), the unavailable case (`available: false`, `note`, don't retry), and the incremental read via `since`. Nothing essential is missing: an agent can call it correctly and interpret the response.

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 schema already documents `since` as 'The `seq` from your previous read. Omit for a full read' (100% coverage). The description adds an important behavioral nuance: passing `since` yields a cheap `unchanged` answer when nothing moved. This clarifies the parameter's practical purpose beyond the raw schema.

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 starts with 'Read the user's SYNCED shopping list', giving a specific verb and resource, then enumerates the contents (lines, crossed-off state, aisle, recipe sources). It explicitly distinguishes the shared synced list from the phone-only list, and the use of 'SYNCED' plus the sibling tool names (add/update/build) makes its scope unambiguous.

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 gives concrete triggers: 'Use it to answer "what's on the list?" or before ticking things off.' It also tells the agent not to retry when `available` is false and notes the phone-only list is not visible. However, it never names a sibling alternative (e.g., add_to_shopping_list for writes), so the 'vs alternatives' part is only implicit.

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