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

The annotations already communicate readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds no behavioral context beyond restating that it lists settings; it does not mention pagination behavior, filtering, or whether the result set is scoped by companyName.

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 short but under-specified rather than concisely informative. A single sentence that restates the tool name does not count as an appropriately compact definition of an 8-parameter tool.

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?

With no output schema, a single required parameter, 8 total parameters, and many related sibling tools, the description should clarify what settings are listed, which company context is required, and how this differs from nearby "settings" tools. None of that is present.

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 description coverage is only 50%, and the description does not compensate for the undocumented parameters. It adds no meaning to top, page, skip, or pageSize, nor clarifies the relationship between companyName and connectionRef.

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?

"Lists BRC company settings" is essentially a tautology of the tool name and title. It does not say what kind of settings are returned or how they differ from settings exposed by sibling tools such as brc_get_company_processing_settings, brc_get_company_reference_settings, and brc_get_company_setup_config.

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 gives no when-to-use or when-not-to-use guidance. There is no mention of alternatives, no mention that companyName is required, and no clarification of how this list relates to the other company settings operations.

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