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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only the cryptic sentence about MCP approval requirements being org-configurable and business workflow approvals always applying, which is ambiguous and never explains whether the step is inserted or appended, whether stepNumber must be unique, or what conflicts on repeated calls.

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 core operation front-loaded and no padding. The second sentence is of dubious value, but nothing is wasted verbosity-wise.

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?

An output schema exists so return values needn't be explained, but for a non-idempotent mutation with a nested data object at 0% schema coverage, the description omits ordering semantics, uniqueness of stepNumber, and how the step interacts with the parent flow. It is not sufficient for correct invocation beyond the bare name and target resource.

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% and the description never mentions flowId or the nested data fields (stepNumber, name, maxApprovalAmount, requireAllApprovers). With a nested object and no schema-level descriptions, the description had to compensate for the coverage gap and does not.

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?

"Add an approval flow step" gives a specific verb (add) and resource (approval flow step), distinguishing it reasonably from create_approval_flow, which creates the parent flow. It stops short of stating that the step is attached to an existing flow via flowId, but the intent is decipherable.

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?

There is no guidance on when to use this versus create_approval_flow, update_approval_flow, or a template-based alternative. The second sentence discusses who configures approval requirements but never states a usage condition or exclusion, so the agent must infer context.

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