mealie_get_shopping_item

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'Fetch' clearly indicates a non-mutating read operation, which is useful. However, it does not detail response format, errors, or permissions, though the presence of an output schema mitigates this. It adds minimal context beyond the verb.

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 sentence of six words, with no filler or redundancy. It front-loads the verb and resource, making it immediately clear what the tool does.

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 one-parameter fetch tool with an output schema, the description is sufficient to understand purpose and invocation. It specifies the object (household shopping list item) and criterion (id). It could mention potential errors or prerequisites, but such details are not essential for this straightforward operation.

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 provides no parameter descriptions (0% coverage), so the description must compensate. It states 'by id', which clarifies that item_id is the identifier, but adds little beyond the parameter name. It does not specify format, source, or how to obtain the ID, leaving a gap.

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 the specific verb 'Fetch' and identifies the resource as 'one household shopping list item by id', clearly distinguishing this from sibling tools like mealie_get_shopping_list (list) and mutation tools. It precisely states what the tool does in a single sentence.

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 implies usage when you have an item_id to fetch a specific item, but does not explicitly mention when to use this versus alternatives like mealie_get_shopping_list or list_shopping_items. No exclusion or alternative guidance is provided.

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