rh_get_capabilities

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

With no annotations, the description carries the full behavioral burden. It does disclose one meaningful trait — the response will not expose secrets — which signals a safe, read-oriented operation, but it says nothing about permissions, side effects, or output stability.

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 tight sentence with no filler, and the security constraint is placed at the end where it reads as a qualifier. Efficient, though the front-loaded content is a bit abstract rather than actionable.

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?

There is no output schema, no annotations, and two undocumented parameters, yet the description does not explain what 'capability evidence' is returned, nor how backend/profile shape the result. For an introspection tool with zero structured support, this leaves real gaps.

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 description coverage is 0%, so the description must compensate and does not. It never mentions the 'backend' parameter (with its workflow_api/comfy_proxy/standard_model enum) or the 'profile' parameter, leaving an agent unable to know what either filters or selects.

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 (report) and concrete resources (local server, catalog provenance, backend capability evidence), so an agent can tell this is a read-only capability/introspection tool. It does not, however, differentiate itself from siblings like rh_get_integration_guide or rh_get_model_schema, and 'capability evidence' is somewhat abstract phrasing.

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 indication of when to call this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer that this is a discovery/introspection step from the name alone.

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