mdl_custom_lists_create

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the mutating character is known. The description adds two facts annotations do not: it requires host-configured MyDramaList authentication, and it changes remote data. However it does not explain reversibility, error modes, or what the created list looks like.

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?

Two short sentences with the auth prerequisite and usage restriction front-loaded. Efficient, though slightly telegraphic style ('Custom Lists: create.') is a minor readability cost.

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 an 8-parameter mutation tool with no output schema and 0% parameter description coverage, the description is far too sparse. It omits required-parameter guidance and any explanation of the seven optional parameters, leaving the agent under-informed for correct invocation.

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% across 8 parameters, so the description should compensate but does not. Nothing is said about 'type', 'sort_by', 'list_type', 'vote_limit', 'max_num_items', or 'add_permission' semantics, leaving the agent to infer meaning from terse titles 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?

States 'Custom Lists: create', which identifies a verb and resource, but adds nothing about what a custom list is or how it differs from direct siblings like mdl_custom_lists_edit. The name itself carries most of the clarity.

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?

Provides a real usage constraint ('use only for an explicit user request'), which is meaningful for a mutation tool. But there is no guidance on alternatives or prerequisites beyond that; siblings like mdl_custom_lists_edit are not referenced.

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