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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that this both validates AND prices, which is more than a plain read, but says nothing about failure behavior or what a failed validation means.

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?

A single front-loaded sentence with zero wasted words. It is efficient, though arguably too terse for a four-required-parameter tool, which keeps it short of a 5.

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 tool taking a nested authoring graph and three identifiers, with no output schema, the description should explain what validation reports and how pricing is expressed. Instead it stops after one clause, leaving output shape and error semantics undocumented.

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 only 50%: graph and board_id are documented, but workflow_id and version_id carry only a UUID pattern with no meaning. The description adds no parameter context at all, so it fails to compensate for the coverage gap.

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 two specific verbs (validate, price) against a clear resource (the automation/recipe being edited), so the agent knows it is a preflight check rather than a read or save. However it never names sibling tools like mcp_recipe_save_draft or mcp_workflow_contract, so differentiation must be inferred.

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 phrase 'being edited' faintly implies it belongs in the edit flow, but there is no explicit when-to-use, no prerequisite (e.g. a recipe must already be open), and no mention of alternatives. An agent gets no routing guidance.

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