gcp_sql_proxy

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

Annotations are minimal (readOnlyHint=false). Description fails to disclose that starting a proxy blocks the process, requires Cloud SQL Admin API, or that stopping terminates the connection. Behavioral traits are underspecified.

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?

Very short but mixes Korean and English, with tags in the middle. Could be more concise by focusing on English and structuring the purpose clearly.

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?

For a tool managing a proxy lifecycle with 5 parameters, the description lacks essential context: behavior of start/status/stop, blocking nature, required permissions. Incomplete even with high schema coverage.

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 descriptions already cover all parameters. The tool description adds no extra meaning (e.g., explaining action lifecycle or port defaults). Missed opportunity to compensate.

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 it runs Cloud SQL Proxy to connect locally, with tags reinforcing the purpose. However, it doesn't distinguish from sibling tools like gcp_sql_query, though none directly overlap.

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, prerequisites, or context for each action (start/status/stop). The agent must infer from parameter names.

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