blockbench_save_project

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

Minimal disclosure. Does not mention overwrite behavior, error handling, or required state (e.g., unsaved changes). With no annotations, the description should provide these 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?

Single sentence with no wasted words, but could include more relevant detail without becoming verbose.

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?

Lacks output schema, no param descriptions, and insufficient behavioral context for a save operation. Does not address common concerns like file overwrite or success indication.

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 coverage is 0%, but description adds no explanation for the 'path' parameter. Agent cannot infer whether it expects full path, filename only, or extension requirements.

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?

Clear verb 'Save', specific resource 'active project', and output format '.bbmodel file' with location 'on the local machine'. Differentiates from siblings like export_model or open_project.

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 like export_model or capture_preview. No prerequisites or context provided.

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