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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds behavioral nuance by stating it 'does not promise acceptance or results,' clarifying that it is a guidance-only tool and not a commitment. This goes beyond the annotations and helps set agent expectations.

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?

The description is three sentences with no filler. It front-loads the usage condition, then states the return value and a key limitation. Every sentence adds value and directly informs the agent's decision to call it.

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 no output schema, the description should explain the return format in more detail. It says 'returns the fit boundary and the information needed before any implementation,' but does not specify the structure or content of that boundary. The parameter semantics are also unaddressed, leaving the agent to guess how to fill the four fields. Given the tool's moderate complexity, the description covers the high-level purpose but misses critical operational details.

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 provides no information about the four parameters (problem, recurrence, consequence, current_approach). The agent has no hints about what values these should take, their formats, or their relationships to the tool's behavior. The description mentions 'recurring workflow' but does not map that to the 'recurrence' parameter, so it fails to compensate for the absent schema descriptions.

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?

The description states a specific purpose: to assess whether 'Quiet Stance' fits a real recurring workflow problem. It enumerates the problem types (delay, rework, waiting, manual coordination, etc.) and clearly states what it returns (fit boundary and info needed before implementation). It also distinguishes itself from a sibling by noting it does not promise acceptance or results.

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 description explicitly opens with 'Use when a person or organization has a real recurring operational workflow with...' which provides clear conditions for invocation. It does not explicitly mention when not to use it or mention the sibling tool 'submit_workflow_inquiry' as an alternative, but the context implies this is for assessment prior to submission.

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