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

Annotations already declare a non-destructive, open-world mutation, but the description adds what those annotations cannot: submissions are stored privately for human review, never auto-published, and require explicit user approval via the user_approved flag. It also sets content constraints (only listed tools, fictional companies, restricted links).

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 trigger with 'Use when', then the approval gate and content rules. Dense but every sentence carries actionable constraints; the final sentence is somewhat run-on with a list of content rules, costing a point.

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?

A mutation tool with no output schema — the description supplies what would otherwise be missing: privacy/destination of the submission, the human review loop, the approval precondition, and format expectations. An agent would not need to ask anything else before calling.

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 coverage is 100%, so the baseline is 3, and the description earns above that: it describes the expected markdown structure (steps, fictional sample output, what goes wrong) and the content rules for tools and links. It adds modest extra meaning without fully restating the schema fields.

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 specific verb and resource: submitting a workflow recipe to mcpforgtm.com for private review. It is unambiguous against the read-oriented siblings (find_recipes, get_recipe, get_recipe_template) because it is the only tool that files content for the site owner.

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?

Explicitly names the trigger ('when the user wants to share a workflow that worked for them'), the prerequisite workflow (show the exact title, tools, roles and text following get_recipe_template), and the gate ('only after they say to send it'). It also clarifies what does NOT happen ('never published automatically').

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