listBusinessEntities

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

With no annotations, the description must fully disclose behavior. It only states 'retrieve a list' without mentioning key traits like read-only nature, authentication requirements, pagination details, or implicit organization filtering via __userContext. This is insufficient for safe agent invocation.

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 a single sentence and front-loaded with the purpose, but it is overly terse given the tool's complexity (3 parameters, no annotations). It sacrifices needed detail for brevity, earning an adequate but not excellent score.

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?

Given the absence of an output schema and annotations, the description must provide comprehensive context. It fails to mention pagination defaults, ordering, scope of entities returned, or any limitations. As a result, the agent lacks sufficient information to invoke the tool correctly.

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 coverage is 100% with descriptions for all three parameters (cursor, limit, __userContext). However, the description adds no extra meaning beyond the schema, such as how to effectively use cursor for pagination or the role of __userContext. Baseline 3 is appropriate.

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 'Retrieve a list of business entities configured for the organization,' specifying verb and resource. It distinguishes itself from sibling tools like getBusinessEntityById (single entity) and other list tools (e.g., listAccounts, listCustomers) by naming a distinct resource type.

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 is provided on when to use this tool versus alternatives, such as when to use listBusinessEntities vs. getBusinessEntityById or listAccounts. The description lacks context about prerequisites or exclusions.

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