brc_clear_company_api_key

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

Description implies mutability (clearing) but does not elaborate on side effects, reversibility, or permissions needed. With no annotations, some burden is on description, but it adequately states the core action.

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?

Single sentence, no fluff, front-loaded with action. Efficient.

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 clear operation with one parameter, description is adequate but lacks explanation of what 'clearing' means operationally (e.g., requires re-authentication).

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 provides full parameter description; description merely echoes 'named company context'. No additional value beyond schema.

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 the verb 'clears' and resource 'API key for named company context', distinguishing it from sibling brc_clear_all_company_api_keys which clears all keys.

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 versus alternatives like brc_clear_all_company_api_keys, or prerequisites for clearing a key.

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