brc_company_readiness_check

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions what the tool highlights but does not state whether it is read-only, required permissions, error conditions, or side effects. This leaves ambiguity for an AI agent about safety and invocation context.

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 two sentences long, front-loads the core purpose, and contains no redundant information. Every word contributes to understanding the tool's function.

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?

The description adequately covers the tool's purpose and key check points, but it does not mention expected return values, prerequisites (e.g., company must be connected), or error handling. Given the simplicity of the tool (one param, no output schema), the description is minimally sufficient but could be more complete.

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 single required parameter 'companyName' is fully documented in the schema with a description and example. The tool description does not add further semantics beyond what the schema provides, so a baseline score of 3 is appropriate given 100% schema coverage.

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 description clearly states the tool's action ('checks readiness'), the target ('connected Big Red Cloud company'), and scope ('read-only and transaction workflows'). It highlights specific considerations (financial-year, VAT, reference-data), distinguishing it from sibling tools that perform operations like batch processing, creation, or deletion.

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 the tool should be used before initiating read-only or transaction workflows, but it does not explicitly state when to use it versus alternatives. It lacks exclusions or references to related tools like brc_start_company_connection or brc_confirm_company_connection, which would clarify prerequisites.

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