shared_lists_update

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write, but the description adds nothing: no auth requirements, no statement of what happens to omitted config keys, no behavior on name collisions. The 'Update' verb is at least consistent with the annotations.

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?

It is short, but its brevity comes from under-specification rather than discipline. There is one sentence that earns nothing beyond echoing the tool name.

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 mutation tool with two required parameters, a nested untyped config object, 0% schema description coverage, and no output schema, the description is completely inadequate. Nothing tells the agent what a valid update looks like or what it changes.

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% and the description explains neither parameter. The opaque 'config' object with additionalProperties and the 'name' pattern/namespace semantics are left entirely undocumented, and the nested config shape is exactly what an agent would need clarified.

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 essentially a restatement of the tool name 'shared_lists_update' as 'Update Shared List'. It names a verb and a resource but adds no scope, no field detail, and no differentiation from siblings like shared_lists_sync, shared_lists_delete, or shared_lists_create. It is a tautology rather than a specification.

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 when-to-use guidance, no prerequisites, and no mention of the alternatives in a large sibling set. An agent gets nothing to decide between update, sync, create, or delete for shared lists.

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