config_set_project

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool sets a default project and returns a status message, implying a persistent configuration change. However, it does not mention permissions needed, side effects, or whether the change is reversible.

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 concise and well-structured with separate sections for summary, arguments, and return value. It contains no extraneous information and is easy to parse.

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 single-parameter setter, the description covers the purpose, parameter meaning, and return type. It lacks usage guidance and prerequisites, but given the simplicity of the tool and the absence of an output schema, it is largely complete.

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?

The description explicitly explains the only parameter, project_id, as 'The ID of the project to set as default', adding semantic meaning beyond the schema which only provides type and title. Since schema description coverage is 0%, this is essential context.

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 function with a specific verb ('Set') and resource ('default Google Cloud project'), making its purpose unambiguous. It is easily distinguished from sibling tools like set_quota_project and list_gcp_projects.

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 implies usage when one needs to set the default project, but it does not explicitly state when to use this tool versus alternatives like set_quota_project. No exclusions or contextual guidance is provided beyond the literal purpose.

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