hcm_list_audit_trail

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

The annotation readOnlyHint=true already signals a read operation. The description adds value by clarifying the exact content (MCP audit trail, not Fusion transaction history) and implies no side effects. It does not describe pagination or response format, but for a simple read-only list tool, the provided context is adequate and consistent with the annotation.

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?

The description is a single, front-loaded sentence with no filler. It efficiently conveys the core function and the key distinction from Fusion history. Every word earns its place.

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 simple read-only list tool with one parameter and no output schema, the description covers the main purpose but leaves the 'limit' parameter unexplained. The agent also receives no guidance on the return format. While the tool is straightforward, the lack of parameter documentation makes it incomplete for optimal usage.

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% and the description does not mention the 'limit' parameter at all. An agent must infer that 'limit' caps the number of results, which is a common convention but not explicitly documented. Since the description does not compensate for the missing schema description, this is a notable gap.

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 states a specific verb ('List') and a resource ('in-process MCP audit trail') and clarifies the scope ('tool invocations; not Fusion transaction history'). This clearly distinguishes it from other list tools and any Fusion-related sibling, leaving no ambiguity about the tool's purpose.

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?

The description gives clear context about what the tool lists and explicitly excludes Fusion transaction history, which helps an agent decide when to use it. It does not name alternative tools, but the distinction is sufficient to prevent confusion with transaction history tools, and the sibling list contains no obvious competitor for this specific function.

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