patch.invert_branch

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

No annotations are provided, so the description carries the full burden of disclosure. The description says 'when supported', implying the patch may fail or be rejected, but does not clarify what makes a branch unsupported for inversion or what happens if it's not supported. No side effects or limitations are mentioned.

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 short sentence which is concise, but it lacks structure and front-loading of key information. It is too brief to be considered optimally concise for an operation that presumably modifies program state.

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 patching branches in a binary analysis context, the description is severely incomplete. There is no output schema, return value information, or behavioral details. The description fails to inform the agent about success conditions, failure modes, or what constitutes a supported inversion.

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%, yet the description adds no meaning to the parameters. The description does not explain what session_id or address represent or how to use them. With only 2 parameters but no schema or description enrichment, the agent has no context on what values to provide.

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 'Patch conditional branch by inversion when supported' states the verb 'patch' and the resource 'conditional branch by inversion', indicating what the tool does. However, it does not distinguish this tool from siblings like patch.assemble or patch.always_branch. The context of 'when supported' is ambiguous and leaves the agent guessing about applicability.

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 provides no guidance on when to use this tool versus alternatives. Sibling tools like patch.always_branch and patch.never_branch offer clearer branch manipulation options, but the description does not explain why one would choose inversion over those. No exclusions or prerequisites are mentioned.

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