getStatus

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

The description explicitly states no auth is required and it's read-only, which is helpful since annotations are absent. It also mentions the HTTP method and path, adding behavioral context beyond the schema.

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 two short sentences, front-loads the key fact (public, no auth), and includes all essential info without waste.

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 zero-parameter, read-only health check, the description covers auth and method. It doesn't explain return values, but output schema is absent, yet for health checks, 'service health' implies a status payload. Adequate given simplicity.

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 has no parameters, so description doesn't need to compensate. However, it gives no info about response format, but for a health check, the description is sufficient.

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 checks service health, a specific resource, and distinguishes it from siblings which are all data-focused. It's not a tautology and provides a clear purpose.

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 it's for health checks but doesn't explicitly state when to use it versus other tools. Since it's a unique health check among siblings, context is enough, but no explicit 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.