list_api_commands

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

No annotations are provided, so the description carries full responsibility for explaining side effects or safety. It implies a read-only listing via the word 'list', but it does not explicitly state that no mutations occur, nor does it explain how a 'specific measurement's commands' would work (e.g., whether a measurement ID is needed). The lack of clarity about return format and edge cases (e.g., invalid area) leaves transparency gaps.

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 efficient and front-loaded with the main action. The parenthetical list of areas is somewhat lengthy but acceptable. The second sentence provides useful context without unnecessary verbosity. No redundancy with schema because the schema does not list these examples (though it has an enum), so the examples add value.

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 one-parameter tool with a rich schema enum and no output schema, the description covers the basic purpose and usage context. However, the problematic 'specific measurement's commands' part is not elaborated or aligned with the schema, and given the sibling tool get_measurement_commands, the description fails to clarify the boundary. This leaves the tool's overall context incomplete.

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 coverage is 100% with a clear enum and description, so the baseline is 3. However, the tool description adds an extra option ('or a specific measurement's commands') that is not present in the schema enum, which actively misleads about valid parameter values. This contradicts the schema and reduces trust in the parameter semantics, so the score is lowered.

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 clearly states it lists raw commands for REW endpoint areas, with a specific verb and resource. However, the inclusion of 'or a specific measurement's commands' creates ambiguity about the tool's exact scope, especially since a sibling tool (get_measurement_commands) likely covers that case. This muddles the distinction and makes the purpose less crisp.

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 a general guideline ('useful to discover REW capabilities not covered by a dedicated tool'), but it contradicts itself by also listing 'specific measurement's commands' as an area when a dedicated sibling tool exists for that purpose. It fails to explicitly clarify when to prefer this tool over alternatives or exclude the overlapping case, leading to potentially inappropriate usage.

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