get_mesh_stats

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

No annotations are provided, so the description carries the full burden. It gives zero behavioral information: no mention of side effects, required Blender state, or what the returned stats represent. An agent cannot infer what this tool does from the description.

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 very short, but it is under-specified rather than concise. It contains only the tool name, adding no actionable information. This is a failure of specification, not efficient brevity.

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?

Even though an output schema exists, the description is completely inadequate for a tool with a parameter and no behavioral disclosure. It does not explain what the tool does, what the output represents, or any preconditions. An agent cannot correctly invoke it.

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 schema includes a single required parameter 'object_name' with no type or description, and schema description coverage is 0%. The description does not clarify what object_name refers to, how to specify it, or any expected format. No compensation is provided.

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 'Blender Studio Pro MCP: get_mesh_stats' — essentially a prefix plus the tool name. It restates the title without explaining what 'mesh stats' means, what statistics are returned, or how this differs from siblings like get_object_info or get_scene_info. 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 guidance on when to use this tool versus alternatives such as get_object_info or get_scene_info. No context about typical use cases or when it would be appropriate.

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