cloud_projs_del

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

Discloses irreversibility and inability to delete default projects. No annotations, so description carries burden; adequately warns about destructive nature.

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?

Two clear sentences plus a structured note. Every sentence adds value, no fluff. Front-loaded with main action.

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?

Covers all essential aspects: operation, scope, constraint, parameter usage. Lacks return value description, but no output schema exists.

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 significant meaning to the key parameter project_id beyond the schema (numeric, resolution logic). Other parameters (extra_headers, etc.) are typical and need no extra explanation.

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?

Clearly states 'Delete a project and all its associated cloud resources across all regions', specifying verb and resource. Distinguishes from sibling tools like cloud_projs_get and cloud_projs_ls.

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?

Provides explicit instructions on how to provide project_id, including resolution from name or default. Does not mention when not to use or alternatives, but the note gives clear context.

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