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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the concrete statement that it 'opens nothing by itself' — resolving the apparent contradiction between the name 'complete' and a read-only tool. It also explains the handoff to browser tools and notes that Planning Center's official API/MCP is mostly read-only, which justifies why this indirect approach exists. It does not describe the shape or length of the returned instructions.

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 core mechanism and the browser handoff are front-loaded and clear, but the trailing sentence about Planning Center's REST API and official MCP server is background justification rather than actionable guidance, and it dilutes an otherwise tight definition.

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 zero-parameter, no-output-schema tool, the description covers what matters: that it returns step-by-step screens/buttons/fields and that a separate browser tool performs the action. The only gap is not characterizing the return payload's structure, which is minor given no output schema exists.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is required and focuses on what the call produces instead.

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 verb and resource (complete a workflow step in Planning Center) and then clarifies the actual mechanism: it returns step-by-step instructions rather than performing the action. That clarification is essential because the name alone would mislead an agent into thinking this mutates data. It stops short of distinguishing itself from the many other planning_center_* action tools, so it is clear but not sibling-differentiated.

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?

It gives a usable two-step pattern: call this to get instructions, then execute with cotlet_browser_* tools in the Cloud Browser. However, it never says when to prefer this over siblings like planning_center_snooze_a_workflow_card or when the browser route is unnecessary, and there are no explicit exclusions.

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