Create Script Project

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

Annotations already indicate non-readOnly and non-destructive nature (creation tool). The description correctly implies creation but doesn't disclose side effects like Drive resource creation or owner resolution via user_google_email, adding minimal value beyond annotations.

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?

Description is a single sentence at 6 words, which is concise but relies entirely on the tool name for context. It could be more informative while remaining efficient.

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?

Despite an output schema existing, the description doesn't indicate what the tool returns. It also doesn't explain the role of parent_id or user_google_email beyond schema descriptions. For a creation tool with multiple parameters, this is insufficient.

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 covers 100% of parameters with descriptions (user_google_email, title, parent_id). The tool description adds no extra meaning to these parameters, so baseline of 3 is appropriate as schema already fully documents them.

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 'Creates a new Apps Script project.' with a specific verb and resource. It distinguishes itself from siblings like create_doc or create_sheet by specifying the project type.

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 such as create_script_project vs create_version or create_sheet. No prerequisites or exclusions mentioned, leaving the agent without decision-making context.

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