set_multiple_text_contents

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 behavioral disclosure. It mentions 'parallelly' (concurrency) but fails to disclose whether existing text is replaced, the atomicity of the operation, error handling, or any side effects. For a mutation tool, this is a significant transparency gap.

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 and scope. There is no wasted wording, though 'parallelly' is an unconventional adverb. It is appropriately sized for the tool's simplicity.

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 simple tool signature with fully documented schema and no output schema, the description is minimally adequate. It conveys the core purpose but omits important operational context such as the effect on existing text contents and failure behavior. The lack of annotations and output schema makes this a clear gap, but the schema compensates for parameter understanding.

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?

The input schema provides 100% coverage with descriptions for both parameters (nodeId and text array). The description adds minimal semantic value beyond the schema, only indicating that multiple contents are set in parallel. The baseline of 3 applies because the schema already fully documents the parameters.

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 identifies the action (set), the resource (multiple text contents), the scope (multiple), and the location (in a node). It distinguishes itself from the sibling tool 'set_text_content' by explicitly stating 'multiple' and 'parallelly'.

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 a clear use case: when you need to update several text nodes at once in a single node. However, it does not explicitly name alternatives or state when not to use it, though the 'multiple' and 'parallelly' wording provides clear context.

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