households_cookbooks_get_one

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

No annotations are provided, so the description carries the full disclosure burden, and it delivers almost nothing: no confirmation that it is a read-only fetch, no note on required auth/permissions, and no failure behavior for an unknown item_id. The word "read-only" appears only inside the keyword spam, which is too incidental to count as deliberate disclosure.

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 first two sentences are reasonably front-loaded and short, but roughly three quarters of the text is an undifferentiated keyword dump listing the tool name, verbs, and resources repeatedly. That bulk adds no information and dilutes the payload.

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 one-parameter read tool with no output schema and no annotations, the description should at minimum say what a cookbook record is and what the call returns. Instead it supplies only the HTTP route, leaving the agent under-informed about the resource and the identifier.

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?

There is a single required parameter, item_id, and schema description coverage is 0% — the schema gives no explanation of it. The description never mentions item_id, so an agent gets no hint that it is the cookbook's UUID versus a slug or name, even though the anyOf allows both.

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 does state a verb and resource ("Get cookbook") and gives the endpoint path, so an agent knows it fetches a single cookbook. However, the leading "Get One — Households: Cookbooks" largely restates the tool name, and there is no differentiation from close siblings like households_cookbooks_get_all or explore_cookbooks_get_one.

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 households_cookbooks_get_all or explore_cookbooks_get_one, nor any precondition for the call. The long keyword list is retrieval fodder, not usage guidance.

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