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

Goes well beyond the annotations: it discloses that nothing leaves the machine in preview mode, that submission enters a moderation queue rather than publishing, who reviews it, and the exact returned shape {status:'submitted', pending:true}. Combined with openWorldHint=true and readOnlyHint=false this gives the agent a complete behavioral picture.

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?

Front-loads the core action and the crucial 'does NOT publish' clarification, then covers preview/submit behavior. It is a dense single block with several defaults and a cross-reference packed in, making it slightly heavier than necessary, but every clause carries information.

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 6-parameter mutation tool with no output schema, the description covers the side-effect model (queue submission, not publication), the preview/submit fork, the return value, and the post-approval lifecycle. Nothing an agent needs to invoke it correctly is missing.

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 100%, so every parameter's meaning is already documented in structured data, establishing a baseline of 3. The description mostly restates the schema (confirm preview semantics, workflow default rule) rather than adding new syntax or edge-case meaning.

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 a precise verb ('Submits') plus the exact resource ('one of YOUR saved recipes/skills') and the destination ('community moderation queue'), and explicitly negates the misreading that it publishes. This clearly separates it from siblings like recipe_save, recipe_install, and recipe_export.

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?

Gives clear operational context: use without confirm=true to preview, with confirm=true to actually submit, and notes the downstream step where recipe_install becomes relevant. It does not spell out when this tool is the wrong choice (e.g. which recipes are ineligible, moderation rejection handling), so it falls just short of full when/when-not guidance.

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