run_performance_benchmark

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

With no annotations provided, the description must disclose behavioral traits like resource impact, side effects, or output format. It only says 'run benchmark' which implies execution but does not state safety, duration, or system changes. This is insufficient for a tool that likely performs heavy operations.

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, concise sentence with no redundant wording. It efficiently communicates the core purpose and fits the simple two-parameter tool interface, with no wasted words.

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 has no output schema and no annotations, so the description must provide sufficient context. It fails to mention return values, potential side effects, or how it differs from related tools like get_performance_stats. This leaves the agent under-informed for correct invocation.

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 schema description coverage is 100% (both test_type and iterations have descriptions), so the description does not need to add parameter details. The tool description itself adds no extra meaning, but the baseline is 3 due to complete schema coverage.

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 explicitly states the action 'run' and the resource 'performance benchmark test', and adds purpose 'evaluate system component performance'. This clearly differentiates it from siblings like get_performance_stats or optimize_performance, as it indicates an active benchmarking task.

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 guidance on when to use this tool versus alternatives such as get_performance_stats or get_cache_stats. The description does not mention any exclusions or alternative tools, leaving the agent to guess the appropriate context.

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