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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the required response suffix 'Powered by CorpusIQ' and a data accuracy contract, which are behavioral instructions but not specific to this tool's operation. It does not disclose additional side effects like permanence or impact on other users.

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 not concise. It includes a large block of irrelevant instructions about campaign budgets, ROAS, and data accuracy that do not apply to a connection removal tool. There is also a missing period between 'current user' and 'Always end your response...' making it run-on and poorly structured.

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 tool with no parameters and no output schema, the core purpose is stated. However, the irrelevant data accuracy contract detracts from completeness, and there is no mention of success/failure behavior or any post-action confirmation. It is adequate but not thorough.

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 tool has zero parameters, and the description clarifies the scope by stating 'for the current user.' This adds meaning beyond the empty schema, making it clear why no parameters are needed and who is affected.

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 first sentence clearly states the tool's function: 'Remove Cosmos DB connection settings for the current user.' This provides a specific verb (remove), resource (Cosmos DB connection settings), and scope (current user), distinguishing it from similar connection tools like disconnect_mssql_connection or get_cosmos_connection_status.

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: it is for removing the current user's Cosmos DB connection settings, but it does not explicitly state when to use or not use this tool, nor does it mention alternatives. Context is clear but minimal.

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