clasp_apis

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

With no annotations, the description carries the full burden. It only says 'List or enable/disable APIs' without disclosing side effects like modifications to appsscript.json, persistence of changes, or whether authentication is required. It also fails to mention the 'open' behavior.

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, short sentence with no wasted words, which is excellent for conciseness. However, it is under-specified by omitting the 'open' action, so it could be improved 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?

The tool has 5 parameters, no output schema, and no annotations, yet the description provides minimal context. It doesn't clarify that it operates on Apps Script API settings, doesn't describe return values, and doesn't mention the 'open' action. This is inadequate for a tool with this complexity.

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 100%, so the baseline is 3. The description does not add any meaning beyond the schema entries, but it also doesn't need to since each parameter is already documented. It doesn't clarify relationships between parameters (e.g., mutual exclusivity).

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's core actions: list or enable/disable APIs. It distinguishes from sibling tools that handle login, cloning, pushing, etc. However, it omits the 'open' action that is present in the schema, so it is not fully comprehensive.

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 is given on when to use this tool versus its siblings, such as clasp_open or clasp_setting. It doesn't specify use cases, exclusions, or when to use list vs enable vs disable.

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