projects_use

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

No annotations exist; description mentions token exchange and saving profile but omits side effects, auth requirements, or reversibility of the state change.

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 sentences, no fluff, front-loaded with purpose and 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?

For a state-modifying tool with 3 params and no output schema or annotations, description lacks details about active profile semantics, consequences, and security context.

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 already describes all 3 parameters at 100% coverage; description adds minor context about token generation but does not significantly surpass schema detail.

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?

Description clearly states it connects to a project and saves as active profile, differentiating from sibling tools like projects_create or accounts_use by specifying project context and token exchange.

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?

Implies usage for switching active project but provides no explicit when/when-not guidance or alternatives among sibling tools like accounts_use or config_use.

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