households_shopping_lists_create_one

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

With no annotations, the description carries the full behavioral burden, yet it only reveals the HTTP method (POST, i.e., a creating mutation) via the endpoint string. It says nothing about required permissions, whether the list body is optional/partial, side effects, or what is returned on success.

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 actionable content ('Create list.' plus the POST path) is front-loaded and adequate, but the trailing keyword block is a long run of near-duplicate tokens ('create, add, new, make, write, post...') that adds bulk without information.

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 creation/mutation tool with no annotations, no output schema, and 0% parameter documentation, the description is too thin. It does not tell the agent what a valid creation looks like, what happens on success/failure, or how it relates to sibling shopping-list tools.

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%, so the schema documents no field meaning, and the description adds nothing about the 'body' object or its nested properties (name, extras, createdAt, update_at). An agent must infer everything about the payload from property names alone.

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 states a clear verb+resource — 'Create list' in the 'Households: Shopping Lists' domain — and the POST endpoint confirms the operation. It does not differentiate itself from siblings like households_shopping_lists_get_all or _update_one beyond the name, but the core purpose is 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?

There is no statement of when to use this tool versus alternatives (e.g., get_one, update_one, or adding items via add_recipe_ingredients_to_list). The keyword list merely restates the name and HTTP verb, offering no conditional routing guidance.

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