Export Three.js project

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

With no annotations provided, the description must bear full transparency burden. It states the tool 'Returns a bounded JSON export' but does not disclose side effects, authorization requirements, whether it is read-only, or what 'bounded' means. This leaves key behavioral traits unexplained.

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 a single sentence of 12 words. It is front-loaded with the action ('Returns') and contains no filler or redundant phrasing, making it highly concise.

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 tool is simple (1 parameter, output schema exists) and the description covers the output's content ('saved project and original assets'). However, it lacks crucial context about error handling, the meaning of 'bounded,' and any side effects, which is especially important given no annotations. This gap prevents a higher score.

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 description does not mention projectId or explain its meaning or constraints. Since there is only one required parameter, the description should clarify what it represents, but it does not add any value beyond the schema's pattern field.

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 uses a specific verb 'Returns' and identifies a clear resource: 'a bounded JSON export containing the saved project and original assets.' This distinguishes it from siblings like pull_project or save_project_copy by emphasizing a full export of project data and assets as JSON.

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 explicit guidance on when to use this tool versus alternatives appears. The purpose is implicitly clear (use when you need a project export), but there are no exclusions or mentions of overlapping tools like pull_project, making usage somewhat implied rather than directed.

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