aaa-health-check

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

The description adds valuable context beyond annotations: it specifies that no credentials are required, which isn't covered by readOnlyHint or idempotentHint. Annotations already indicate it's safe (read-only, idempotent), so the bar is lower, but the credential-free aspect is a useful behavioral trait that enhances transparency.

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 a single, efficient sentence that front-loads the key information: it states what the tool does and a critical constraint (no credentials needed). Every word earns its place, with no redundancy or unnecessary details.

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 tool's simplicity (0 parameters, no output schema) and rich annotations (readOnlyHint, idempotentHint), the description is nearly complete. It covers purpose, usage, and a key behavioral trait. A minor gap is the lack of detail on what 'server status' includes, but with annotations ensuring safety, this is acceptable.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description reinforces this by stating 'without requiring any credentials,' which aligns with the empty input schema, adding clarity that no inputs are needed for this operation.

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 explicitly states the verb ('Returns') and resource ('server status'), making the purpose clear. It also distinguishes itself from siblings by specifying it doesn't require credentials, which is unique among the listed tools that mostly involve data manipulation or retrieval requiring authentication.

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 provides explicit guidance on when to use this tool: for checking server status without credentials. It implies an alternative scenario where other tools might require credentials, helping differentiate it from siblings that likely need authentication for operations like create, delete, or search.

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