kin_transaction_stage

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation profile is partly covered. The description adds genuinely useful behavior beyond that: an 'update' replaces the whole body rather than patching it. It omits the most consequential staging fact, that nothing lands until kin_transaction_commit and can be discarded by kin_transaction_abort. No contradiction with 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?

Three short sentences, front-loaded with the operation, then the verb glossary, then the one non-obvious rule plus the pointer to get_entity_source. No padding.

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 transaction-staging tool with no output schema and a large polymorphic operation union, the description covers the verb model but not the lifecycle (commit/abort, atomicity, ordering of operations) or the structured Entity/Relation shape. Adequate, but an agent still has to infer how staged work is applied.

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 a conceptual verb taxonomy, but it says 'four verbs' while the schema accepts many aliases (replace/overwrite/move/add/upsert) across six operation shapes, including the structured Entity/Relation mutation, none of which the summary mentions. The framing is helpful but incomplete against the schema.

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 first sentence gives a specific verb and resource: stage mutations onto an open transaction. The verb glossary ('create' admits a file, 'update' changes an entity, 'delete' retires one, 'rename' moves one) sharpens what the tool does. It does not explicitly differentiate itself from kin_mutate, which is the obvious sibling it could be confused with.

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 makes the prerequisite ('an open transaction') explicit and routes one case to a sibling: read with get_entity_source before an 'update'. It stops short of stating when to use this over kin_mutate, or what happens if no transaction is open.

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