Cm Info

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

No annotations are supplied, so the description carries the disclosure burden. It implies a passive read that returns version and status data, but it says nothing about permissions, side effects, or whether the call is cheap. For a zero-parameter informational tool with an output schema covering return values, this is adequate but thin.

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 short sentence that front-loads the three returned items with no filler. It is efficient, though the sentence-fragment style and Portuguese-only wording give no structural aids beyond the enumeration.

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?

The tool is simple: no inputs and an output schema that documents returns. The description enumerates what the response contains, which is enough for an agent to decide to call it. Only the lack of usage context keeps it below a 5.

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 no parameter semantics to explain; baseline 4 applies. The input schema confirms an empty object with additionalProperties false.

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 the specific resources returned: Cloudera Manager version, API version in use, and general CM status. That is a clear verb-less but unambiguous 'retrieve info' purpose. It does not explicitly contrast with siblings like cluster_health_summary or cm_api_get, so it stops short of a 5.

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 when-to-use guidance, no exclusions, and no mention of alternatives such as cluster_health_summary or cm_api_get. The only implied usage context is that the agent should call it when it wants version/environment facts about the CM server itself.

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