list_business_agent_tools

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

With no annotations provided, the description carries the full behavioral transparency burden. It adds useful context: the list is scoped to 'the authenticated API project' and filtered to 'eligible' tools, which implies not every installed tool may appear. However, it does not disclose response format, pagination, or what 'eligible' means, leaving some behavioral ambiguity for a no-output-schema tool.

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?

Two concise sentences with no filler. The core action and resource are front-loaded, and the usage hint is appended as a separate helpful clause.

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 zero-parameter list tool, the description covers the essential context: what is listed, for whom, and why it might be used. The lack of output schema and annotations makes the vague term 'eligible' a minor gap, but overall the tool is simple enough that the provided context is nearly 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 tool has zero parameters and schema coverage is 100%, so there is nothing for the description to add about parameter meaning. Baseline 4 is appropriate because no parameter documentation burden exists.

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 opens with the specific verb 'List' and a precise resource: 'eligible Business Agent tools installed for the authenticated API project.' It clearly distinguishes this discovery tool from sibling tools like list_business_agents, which list agents rather than tools/connectors.

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 explicitly says 'Use to discover connectors/tools available for business agent creation,' providing clear context for when to call the tool. It does not name an alternative or state when not to use it, but the purpose is specific enough that an agent can identify the right scenario.

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