ocp-advisor__get_info

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value beyond that: it discloses the endpoint is unauthenticated (no auth setup needed), names the internal services queried (Smart Proxy, Insights Results Aggregator, Content Service), and states the negative boundary that no recommendations are returned.

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?

Front-loaded with the core purpose, followed by an actionable call directive and supporting detail. Every sentence earns its place (purpose, action, endpoint/auth details, scope boundary), though the emoji directive and multi-clause last sentence add slight verbosity.

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 diagnostic tool with an output schema present, the description covers everything an agent needs: what it returns, that it needs no auth or information gathering, and what it explicitly does not return. Return-value details are rightly delegated to the output schema.

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; the baseline of 4 applies. No parameter documentation is needed or missing.

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?

States a specific verb (Get) and resource (OCP Advisor backend health, deployed rules version, release metadata) in the first sentence. It explicitly distinguishes itself from the advisor__* siblings by declaring it 'does not return Advisor recommendations or cluster findings.' An agent can route correctly without opening any schema.

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?

Provides clear when-to-use context ('service diagnostics, release verification, and backend health checks') and a strong call directive ('CALL IMMEDIATELY - No information gathering required'). It also gives an implicit when-not by excluding recommendations/findings, though it does not name a specific alternative tool to use instead.

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