maintenance_off

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

No annotations are provided, so the description carries the full burden. It mentions 'handles service restoration and process resumption' which adds some behavioral context beyond the basic action, but doesn't specify authentication requirements, error conditions, or what 'restoration' entails in detail. It adequately describes the mutation effect but lacks depth on implementation specifics.

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 well-structured with a clear opening statement followed by a bulleted list of use cases and a summary sentence. Every sentence adds value, though the final sentence slightly repeats earlier points. It's appropriately sized for the tool's complexity without unnecessary elaboration.

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 single-parameter mutation tool with no annotations or output schema, the description provides good context: clear purpose, usage guidelines, and behavioral hints. It covers the essential 'what' and 'when' but lacks details on error handling or return values. Given the tool's simplicity, this is nearly complete, missing only minor operational specifics.

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 schema description coverage is 100%, fully documenting the single 'app' parameter. The description doesn't add any parameter-specific information beyond what's in the schema, but with only one well-documented parameter and no complex inputs, this is sufficient. A baseline of 3 is appropriate, but the simplicity elevates it to 4 as no additional clarification is needed.

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 clearly states the specific action ('Disable maintenance mode') and resource ('Heroku applications'), distinguishing it from its sibling 'maintenance_on'. It uses precise language about restoring traffic routing and resuming dyno operations, making the purpose unambiguous.

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 lists four specific scenarios for when to use this tool: restoring traffic routing, resuming dyno operations, completing deployments, and verifying health after maintenance. It distinguishes from 'maintenance_on' by focusing on disabling rather than enabling maintenance mode, providing clear context for selection.

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