generate_harmony_patch

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

With no annotations, the description carries the full behavioral burden: it does not say whether a file is written to disk or source text is returned, whether the target assembly must already be loaded, whether an existing patch class is overwritten, or how errors surface. 'Correct' is asserted but not explained.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity contributes to the missing guidance rather than being a virtue of precision.

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 six-parameter code-generation tool with no annotations and no output schema, the one-line description is insufficient: the agent cannot tell what is produced (file vs. code), where it lands, or what prerequisites exist before calling it.

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 all six parameters (including patch_type default 'both' and parameter_count for overload disambiguation) are documented in the schema itself. The description adds no parameter meaning beyond what the schema provides, which is the baseline 3 case.

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 gives a specific verb (generate) and resource (Harmony patch class) scoped to a specific method, so the agent knows the outcome. It does not, however, distinguish this from siblings like validate_patch_target, list_patchable_methods, or generate_plugin, which also operate on patch targets.

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 when-to-use guidance, no preconditions (e.g. whether the assembly must be loaded first via load_assembly), and no mention of alternatives such as validate_patch_target or compile_plugin. The agent must infer the entire workflow position of this tool.

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