health_catalog

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description's contribution is disclosing the shape of the payload (types, fields, operations, permissions), which is genuinely useful, but it says nothing about caching, completeness guarantees, or whether the catalog reflects server-side configuration changes.

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?

A single front-loaded sentence with no filler; the resource and the enumerated contents come first. Nothing in it is redundant with the name or annotations.

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?

With no output schema, the description usefully stands in for one by listing the four kinds of information returned. For a zero-argument, read-only catalog tool that is nearly sufficient; the only real gap is the missing distinction from health_schema, which matters given how many sibling discovery tools exist.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The sentence correctly refrains from inventing filtering or pagination parameters that the empty schema does not support.

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 names a specific verb and resource — it enumerates the writable data types, fields, operations and required permissions that the catalog returns — so an agent knows exactly what this tool produces without opening a schema. It is clear, but it never contrasts itself with the closely-named sibling health_schema, so sibling differentiation is left to inference.

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?

There is no statement of when this catalog should be consulted versus health_schema, health_status or health_list, all of which sound adjacent. The 'writable' qualifier implies a discovery use case, but no condition, prerequisite or alternative is spelled out.

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