connection_status

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

No annotations are supplied, so the description carries the full burden, and it does disclose the two things being probed (credential configuration and connectivity), implying a safe read-only operation with no side effects. It says nothing about required permissions, failure semantics, or network behaviour, which for a zero-parameter, annotation-free tool is thin but not seriously deficient given an output schema exists.

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?

A single sentence with no filler, and the core action ('Check') is front-loaded. Nothing here is redundant or padding.

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 tool is trivially simple — no parameters, no nesting, and an output schema that already explains the return values — so the description does not need to cover return shape or outcomes. The only real omission is routing guidance relative to sibling diagnostics, which is a usage rather than a completeness gap.

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 takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies, and the schema is trivially complete.

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 gives a specific verb-and-object pair — checking whether Bullhorn API credentials are configured and connectivity is available — which is far more precise than the bare name 'connection_status'. It does not, however, differentiate itself from near-neighbour diagnostics such as setup_status or bullhorn_session, which an agent would reasonably confuse it with.

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 when-to-use, when-not-to-use, or alternative routing is stated. The diagnostic framing implies a pre-flight check, but with setup_status and bullhorn_session in the sibling set the agent is given no basis to choose between them.

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