run_cloudcompare_command

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

No annotations are provided, so the description carries the full burden. It discloses that the executable path and -SILENT are added automatically, but does not mention output format, error handling, or potential risks, which are important for arbitrary command execution.

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 extremely concise with two sentences that cover purpose and a key usage guideline. Every word is essential with no redundancy.

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?

Given the complexity of running arbitrary commands, the description lacks critical information such as what output is returned (e.g., stdout/stderr), success/failure indicators, and potential risks. No output schema is provided, so the description should compensate but does not.

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 the baseline is 3. The description adds value by providing an example and explicitly stating what not to include, which goes beyond the schema's description of arguments 'after the binary and -SILENT'.

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 'Run an arbitrary CloudCompare CLI command' with a specific verb and resource. It distinguishes itself from siblings by targeting advanced/unsupported operations, as siblings like compute_cloud_to_cloud_distances are specific known tasks.

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 explicit guidance on what not to include (executable path and -SILENT). While it implies usage for cases not covered by siblings, it does not explicitly state when to use or provide alternatives, but the context is clear.

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