Get HA resource status

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds 'current HA manager state', indicating a snapshot. No additional behavioral details (e.g., error behavior, required permissions) that go beyond annotations. Adequate given 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?

One sentence of 8 words, front-loaded with verb and resource. No redundancy or extraneous information. Efficiently communicates the core function.

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 simple read-only tool with one parameter and no output schema, the description is mostly complete. It could mention what 'state' entails or possible statuses, but given annotations and schema coverage, it provides sufficient context for correct invocation.

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 coverage is 100% for sid, with its description providing examples. The tool description does not add extra semantic information about the parameter beyond what the schema provides. Baseline score applies.

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?

Description states 'Get the current HA manager state for a single resource.' Verb 'get' and specific resource (HA manager state for a single resource) clearly define purpose. It distinguishes from sibling 'get_ha_status' (likely global HA status) and 'list_ha_resources' (list all resources).

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?

No explicit when-to-use or when-to-avoid guidance. The implication is that it's for a single resource identified by sid, but alternatives like 'get_ha_status' or 'get_ha_group' are not mentioned. Minimum viable clarity.

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