add_marker

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 reveals nothing about side effects, required permissions, or behavior (e.g., whether it adds a marker to the current frame, requires an active scene, etc.). The description is entirely uninformative.

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 extremely short, but this is under-specification rather than effective conciseness. It provides no useful information, so its brevity does not help. It earns a 2 because it is technically concise but fails to convey anything meaningful.

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?

With no annotations, no output schema details, and incomplete parameter information, the description is completely inadequate for an agent to successfully call this tool. An agent would have no idea what 'add_marker' does or how to fill in the required 'name' parameter.

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%, and the input schema shows parameters 'name' and 'frame' with no explanations. The description does not add any meaning to these parameters, leaving the agent with no idea what values to provide or their purpose.

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 simply 'Blender Studio Pro MCP: add_marker', which restates the tool name without any verb or resource detail. It fails to state what the tool actually does, such as adding a marker in Blender, and does not distinguish it from sibling tools like list_markers or remove_marker.

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 guidance on when to use this tool versus alternatives, no context about prerequisites, and no mention of related operations like removing or listing markers. The description provides zero usage direction.

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