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

Goes well beyond the annotations: billing stops while Paused, unused days from pause date to Paid Until Date are credited on resume, and the next bill date shifts out accordingly. It also discloses the per-call confirmation default, that it reaches other people, and the API key/access requirement – exactly the mutation consequences an agent needs.

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-loads the purpose and keeps related billing/resume mechanics together. It is somewhat dense with several distinct ideas (credit math, confirmation, auth), but every sentence carries operational value rather than filler.

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 mutation tool with no output schema, the description covers the mutation effect, the resume-side billing consequences, confirmation behavior, and auth requirements – nothing an agent needs to call it correctly is missing.

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 100%, so the schema already documents all four parameters, including that resume_on empty means indefinite. The description reinforces resume semantics but adds little parameter syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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 and resource ('Pause a member's plan and its billing') and adds the UI path ('Runs Pause Plan from the member profile'). An agent can distinguish it from pushpress_cancel_member_plan and pushpress_switch_member_plan without opening schemas.

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?

Gives clear usage context ('Leave resume_on empty for an indefinite pause') and confirmation/authorization guidance. It does not, however, explicitly name cancel_member_plan or switch_member_plan as alternatives or state when-not to pause, so routing is left to inference.

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