manifest.patch_row

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

Annotations already indicate readOnlyHint=false, destructiveHint=false. The description adds 'through the overlay only', hinting at a behavioral constraint, but does not fully disclose outcomes like overwrite behavior or error conditions. Some additional context is provided beyond annotations.

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 sentence, concise, and front-loaded with the key action. However, it is too brief to be maximally useful, lacking necessary detail without being wasteful.

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 (nested objects, 0% schema coverage, presence of an output schema), the description is insufficient. It does not explain the overlay concept, the patch structure, or the response format, leaving substantial gaps.

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?

With 0% schema description coverage, the description must explain parameters, but it does not. It omits any explanation of what the 'patch' object can contain, or the roles of 'job_id' and 'row_id'. This leaves significant ambiguity for an agent.

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 the verb 'Patch', the resource 'one manifest row', and the scope 'through the overlay only'. It effectively distinguishes this from sibling tools like manifest.batch_patch (batch operation) and manifest.get (read).

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 implies usage for a single row patch via the overlay, but does not explicitly state when to use this tool versus alternatives or provide any exclusions. The context of sibling tools suggests batch alternatives, but guidance is lacking.

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