shared_lists_create

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the safety profile is thin. The description adds nothing about the creation semantics: whether names must be unique, whether the call is idempotent, what the config object governs, or what side effects creation has. It does not contradict the annotations, but it carries almost none of the behavioral burden.

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?

Three words, zero waste, front-loaded with the action. There is nothing extraneous, but the brevity reflects under-specification rather than disciplined conciseness, so it lands at the minimum-viable level.

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?

With two required parameters, a nested untyped config object, no output schema, and only minimal annotations, the description leaves an agent with no idea what a valid config looks like or what the call returns. Far more context is needed for a creation tool of this shape.

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 description must compensate for two undocumented parameters and it does not. The config object is a free-form nested object (additionalProperties: {}) that is completely opaque, and the name pattern/minLength constraints are only inferable from the raw schema, not explained anywhere.

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?

"Create Shared List" is a tautological restatement of the tool name shared_lists_create. It conveys the bare verb+resource but offers no scope, no differentiation from siblings like shared_lists_update or shared_lists_sync, and no explanation of what a shared list actually is.

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 gives no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling tools (shared_lists_list, shared_lists_get, shared_lists_update). Nothing tells the agent when this is the right call.

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