Export configuration (SCP)

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with 'no settings change' while adding genuinely new facts: it runs as a short export job and takes 30-120 seconds, which matters for timeout planning. It does not cover failure modes (e.g. what happens if save_path exists) though that constraint lives in the schema.

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 compact sentences, front-loaded with what gets exported, then uses, then runtime/cost. No filler, though the thermal-profile clause is slightly parenthetical and could be trimmed.

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, but the description characterizes the return payload ('every setting as XML') and the duration, which is the operationally important unknown. Minor gap: it doesn't note that the response may be truncated by max_chars or saved to disk via save_path, leaving that to the 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?

Schema description coverage is 100%, and each parameter's enum and truncation semantics are already documented there. The description contributes only the implicit XML emphasis, so the baseline of 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 ('Export the Server Configuration Profile') and enumerates exactly what is included: 'every iDRAC, BIOS, NIC and RAID setting as XML'. This clearly separates it from sibling readers like idrac_get, idrac_bios_attributes or idrac_thermal, which cover narrow slices.

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 concrete use cases: backup, settings comparison, and reading iDRAC settings such as thermal profiles that 'have no other Redfish view'. That implicitly routes the agent here over the narrow per-component siblings, but there is no explicit when-not guidance or named alternative.

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