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

Annotations already disclose the safety profile (mutation, idempotent, non-destructive), which lowers the bar. The description adds a genuine data-handling note ('privacy-filtered project metadata'), but says nothing about what the update changes, what happens to omitted fields, or what permissions are required.

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 sentence with no filler, so it is appropriately sized. However it is not well front-loaded in a useful way — the ambiguous noun phrase leads, and the clarifying context never arrives.

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 6-parameter mutation with a nested details object, no output schema, and many sibling instruction tools, the description leaves critical gaps: no effect semantics, no scoping rules, and no routing among the analogous instruction tools. It is not adequate for the complexity of the call.

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 no parameter-level meaning beyond it. This is the correct baseline, though several schema field descriptions (status, sessionId, executionId all read 'Owned project ID ...') are copy-paste errors that the description does nothing to correct.

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 names a verb ('Update') and a resource ('hosted submit node instruction'), but 'hosted submit node instruction' is opaque jargon and the verb conflicts with the tool name ('submit' vs 'Update'). It also fails to distinguish itself from near-neighbors like queue_instruction_tasks, control_instruction_task, and acknowledge_instruction_control, so an agent cannot tell which instruction tool applies here.

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 prerequisites, and no named alternative, despite many sibling tools that also manipulate instructions or node work. The only hint is the phrase 'using privacy-filtered project metadata', which describes input sourcing rather than invocation conditions.

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