households_shopping_lists_create_one

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

The description gives no behavioral information whatsoever. It does not mention side effects, idempotency, authorization requirements, or any constraints. Since there are no annotations, the description carries the full burden and completely fails.

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?

While the description is short, it sacrifices essential information. True conciseness would include key details about the tool's function and parameters.

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?

Given the lack of annotations, output schema, and parameter descriptions, the description is severely inadequate for an agent to use the tool correctly. It omits required information about the body structure and the outcome of the 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 input schema has 0% description coverage, and the description does not explain any parameters. The 'body' parameter and its nested fields (name, extras, etc.) are entirely undocumented in the description.

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 is just 'Create One' plus the endpoint path. It fails to explicitly state what is being created (a shopping list), relying on the tool name. It does not distinguish from sibling tools like create_many or other create_one tools.

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 guidance is provided on when to use this tool versus alternatives such as households_shopping_lists_create_one vs households_shopping_lists_update_one, or create_many. No context on prerequisites or exclusions.

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