Read any Redfish resource

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious behavioral fact that responses are JSON and are silently truncated at max_chars, which is important because truncation can produce incomplete data. It doesn't describe how errors or unsupported $expand/$select are reported.

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?

Three short sentences, front-loaded with purpose, followed by the routing rule and the output contract. No filler or restatement of the title.

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 carries the burden of describing returns and does so (JSON, truncated). For a generic read tool with rich annotations and fully documented params, what's left out (error semantics, whether truncation is signaled in the response) is minor but noticeable.

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 100%, so all four parameters (path, expand, select, max_chars) are already documented with formats and defaults. The description reinforces the path example and the truncation role of max_chars but adds no syntax or constraint information beyond the schema. Baseline 3 applies.

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 and resource ('GET any Redfish resource on the iDRAC by path') and includes a concrete example path. The phrase 'use it for data the dedicated tools do not cover' explicitly positions it relative to the many sibling idrac_* helpers.

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?

Gives a clear selection rule: reach for this when the dedicated tools don't cover the data, which is exactly the fallback role a generic GET plays among 17 domain-specific siblings. It stops short of naming preconditions such as authentication needs or what to do when a path returns an error.

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