set_text_body

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

No annotations are provided, and the description carries zero behavioral disclosure. The tool name suggests setting text body text, but there is no mention of side effects, permissions, undo behavior, or return values. The description does not contradict annotations (none exist), but it adds nothing.

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?

While the text is short, it is not concise—it is under-specified. The description is just a prefixed name with no explanatory content. This does not qualify as effective conciseness.

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 tool with two required parameters and no schema descriptions, annotations, or output schema information, the definition is completely inadequate. The agent cannot determine what the tool does, how to call it correctly, or what to expect.

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%, meaning the parameters 'body' and 'object_name' have no descriptions. The tool description itself does not explain these parameters, so the agent gets no semantic guidance beyond the parameter names.

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 is exactly 'Blender Studio Pro MCP: set_text_body', which merely restates the tool name with a prefix. It provides no verb, resource, or action detail, so the agent cannot infer what the tool does. This is a tautology.

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?

No information is given about when to use this tool versus any of the many siblings (like set_attr_path, set_shape_key_value, etc.). There is no mention of context, prerequisites, or exclusions.

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