bc_list_companies

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

Details internal behavior (opens BC Companies system page, reads entries, closes it) and explicitly states no effect on currently open pages or session state. With no annotations, the description fully discloses behavioral traits.

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?

Every sentence is purposeful. The description is front-loaded with the core purpose, followed by usage guidance and behavioral notes. No redundancy or filler.

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 tool with zero parameters and no output schema, the description covers all necessary context: purpose, usage, internal behavior, side effects, and relationship to sibling tools. Nothing is missing.

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 has no parameters, and description explicitly confirms 'No parameters are required.' This adds clarity beyond the empty schema, especially by explaining the absence.

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 'List all companies available' with specific verb and resource. Distinguishes itself from sibling bc_switch_company by indicating its role as a discovery/verification step before switching.

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?

Explicitly says to use before bc_switch_company to verify existence, and not to use if company name is already known. Provides a recommended workflow: bc_switch_company then bc_open_page for working with data.

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