execute_ruby

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

The description discloses that code can modify or delete model data, a key behavioral trait. Without annotations, it carries the full burden and does so well, though it could mention error handling or restrictions.

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 two sentences, front-loaded with purpose and context, no redundant information. Every sentence serves a clear role.

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?

The description provides return information and destructive warnings, but lacks details on error handling, sandboxing, or limitations. Given no output schema, some additional context would be helpful but is not critical.

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 covers the parameter description, but the description adds significant context about the execution context (SU_MCP module, API access) beyond the schema, providing meaningful value.

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 tool executes arbitrary Ruby code in SketchUp, with specific context (SU_MCP module) and API access. It distinguishes from sibling tools which are all modeling operations, not code execution.

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?

While the description warns to use with care, it does not explicitly state when to use this tool vs alternatives. However, no alternative tools exist for code execution, so the lack of explicit guidance is partially mitigated.

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