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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely useful content-level transparency — that it returns the full 'whole' record across three row shapes plus submission/curator/public-page state — which goes beyond what the annotations convey. It stops short of 5 as the row/doctrine vocabulary is undefined.

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-loaded with the core action, but the body is a dense, jargon-laden run-on ('arm row', 'reprompt row', 'doctrine', 'run row') that taxes parsing, and the closing note about Kuro Desktop workflow files is niche. Several clauses don't clearly earn their place.

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 an output schema present, the description needn't detail return values, yet it helpfully frames the record's composition and states the precondition relationship to update_recipe. It is largely complete for a single-parameter read, with the recipe_id source being the main omission.

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% for the single recipe_id parameter, so the description carries the burden of explaining it — but it says nothing about the id's format or where to obtain it (e.g., from list_own_recipes). It only hints at recipe kinds via 'the recipe you own', leaving the required parameter effectively undocumented.

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 (Read) and resource (one recipe you own), and the scope qualifier 'you own' implicitly separates it from the catalog-oriented get_recipe sibling. It never names get_recipe, list_own_recipes, or update_recipe's read complement directly, so differentiation is inferred rather than explicit, and the 'arm row/reprompt row/run row' jargon obscures the plain purpose.

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 gives a use condition with rationale: 'Use this before update_recipe — a patch replaces config, writer or definition whole.' That is a concrete when-to-use directed at a named sibling. It falls short of 5 because it offers no when-not guidance and doesn't distinguish itself from get_recipe or list_own_recipes.

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