get_sql_instance_details

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

With no annotations, the description carries the full burden. It states it returns detailed information but does not disclose potential side effects, permission requirements, or limits. For a read-only getter, this is adequate but does not enrich beyond the obvious.

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 well-structured with Args and Returns sections and is not overly verbose. The opening sentence is concise and informative, though the Args section partially duplicates schema fields.

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 simple 2-parameter getter, the description covers purpose and parameters, but the return value is vaguely described as 'detailed information'. Since there is no output schema, it should provide more specifics about what details are returned. It also lacks any usage context or error behavior.

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 0%, so the description adds meaning. It defines both parameters: 'The ID of the GCP project' and 'The ID of the Cloud SQL instance', giving semantic context that the bare schema lacks. However, it does not include formats or constraints.

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 explicitly states 'Get detailed information about a specific Cloud SQL instance' – a clear verb+resource combination. It distinguishes itself from sibling tools like list_cloud_sql_instances and get_instance_details (which likely refers to compute instances) by naming the specific resource 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that it should be used after listing instances, nor does it contrast with the sibling list_cloud_sql_instances. Usage is only implied by the tool name and the word 'specific'.

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