execute_context_script

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

While 'execute' implies side effects (running a script in Blender), the description does not disclose what changes occur (e.g., scene modifications, object creation) or whether the operation is destructive. No annotations are provided, so the description carries the full burden, but it omits critical behavioral details.

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 relatively concise with a clear structure including 'Args' and 'Returns' sections. It front-loads the primary action. However, the 'Returns' section is vague ('Script execution results') and could be more specific without adding much length.

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 2 parameters and moderate complexity, the description explains the inputs but fails to describe the execution behavior or the structure of the return value. With no output schema, the missing 'Returns' details are a gap. Sibling tools like 'execute_blender_code' are not differentiated, leaving the agent without full context to choose correctly.

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 description adds meaning beyond the schema by noting that script_name excludes the '.py' extension and that category defaults to 'default'. However, it does not clarify where scripts are located, valid category values, or the format of valid script names. At 0% schema coverage, the baseline is lower, but the description provides some helpful clarification.

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 states the action ('execute'), the resource ('previously registered Python script'), and the context ('in Blender'). It distinguishes from siblings like 'register_context_script' and 'list_context_scripts', though it could be more specific about what execution entails beyond running.

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 vs alternatives (e.g., 'execute_blender_code'). No mention of prerequisites such as the script needing to be registered first or that the category must exist. The description is purely parameter-focused without contextual usage advice.

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