get_world_info

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 discloses nothing about side effects, read-only behavior, potential errors, or return format. The description is entirely devoid of behavioral context.

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 not conciseness – it is under-specification. A useful description would at least state the tool's function. This text is just a label and provides no useful structure or front-loaded information.

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 complexity implied by the tool name and the context of many sibling tools, this description is completely inadequate. An agent cannot infer the tool's purpose, inputs, outputs, or behavior, and the output schema is not provided in the visible definition. Nothing about the tool's role is conveyed.

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?

While there are zero parameters (so the schema is trivially complete), the description adds no semantic value. It does not explain what the tool does, what data it returns, or how it relates to the world context. Since the description is the only source of guidance beyond the empty schema, its failure makes it inadequate.

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 merely 'Blender Studio Pro MCP: get_world_info', which is a prefixed tool name rather than a statement of purpose. It does not specify a verb, resource, or what information about the world is retrieved, and it fails to distinguish itself from sibling tools like set_world_background or get_scene_info.

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 typical use cases, and no mention of prerequisites or constraints. The description gives an agent no basis for deciding between get_world_info and other world-related tools.

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