brc_clear_all_company_api_keys

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

No annotations provided; description only states action and scope. Does not disclose side effects, reversibility, authorization requirements, or what 'MCP server memory' means. Lacks behavioral depth.

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, clear sentence with no unnecessary words. Front-loads key action and scope.

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?

Sufficient for a parameterless tool; describes what is cleared and scope. No output schema, so return values not required. Could mention confirmation or reversibility, but overall adequate.

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?

No parameters in schema (100% coverage). Baseline score of 4 for 0 parameters; description adds no param info since none exist.

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?

Clearly states the verb 'clears', resource 'connection credentials for all company contexts', and location 'MCP server memory'. Differentiates from sibling brc_clear_company_api_key by specifying 'all company contexts'.

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?

Does not explicitly provide when to use or alternatives. The distinction from the singular clear tool is implied by name, but no explicit guidance on when to choose this over brc_clear_company_api_key.

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