Enable / Disable Health Rule

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

The description discloses the internal fetch-modify-PUT process, which adds context beyond the annotations. It confirms idempotentHint and non-destructive behavior, and contradicts nothing in annotations.

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 four sentences with no wasted words: purpose, mechanism, arguments, return. Front-loaded with the main action, clear and efficient.

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?

Given the simple toggle operation and complete schema coverage, the description adequately covers behavior and return. It could mention error conditions or prerequisites, but overall it's sufficient for an agent to use correctly.

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 input schema already has 100% parameter description coverage. The description repeats the parameter types but adds no new semantic information beyond the schema. Baseline score of 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?

The description clearly states the tool enables or disables a health rule without changing other settings. It uses a specific verb-resource pair and distinguishes from sibling tools like appd_update_health_rule, which modifies other settings.

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 implies when to use this tool by stating 'without changing any other settings,' differentiating it from update_health_rule. However, it does not explicitly name the alternative tool or provide guidance on when not to use it.

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