list_script_projects

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

Discloses being Drive-backed and lists specific mimeType, but lacks details on auth requirements, rate limits, or error handling. Without annotations, more context is needed.

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?

Concise with clear structure: purpose, limitation, args, returns. Efficient use of words, but could be slightly more streamlined.

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?

Provides high-level return description and limitation, but lacks detail on pagination behavior, error cases, and output format beyond 'formatted string'.

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?

Adds meaning by restating parameter purposes and defaults, but with 0% schema coverage, more detail (e.g., format constraints) would improve.

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?

Description clearly states it lists standalone Apps Script projects from Google Drive, uses specific verb 'list' and resource 'standalone Apps Script projects', and explicitly excludes container-bound scripts, distinguishing it from sibling tools.

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?

Describes limitation excluding container-bound scripts, implying when not to use, but does not provide explicit alternatives or when-to-use guidance.

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