Bridge Connect

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

Adds that it bypasses intent routing and is a low-level direct call, which annotates its behavioral traits beyond the annotations. No contradiction with annotations.

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?

Three sentences front-loaded with purpose, no redundancy or waste.

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 presence of output schema, description covers critical usage context (bypass routing, known organ/tool). Could mention advanced user assumption, but not necessary.

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 high (83%), and description only adds naming conventions and that organ and tool_name are required. Doesn't elaborate on other params, but baseline is adequate.

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?

Clearly states it's a low-level direct organ tool call that bypasses intent routing, requiring organ and tool_name known ahead of time. Distinguishes from siblings by emphasizing directness.

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?

Explicitly says use only when organ and tool_name are known ahead of time, implying when not to use. Lacks explicit naming of alternative tools, but context from siblings provides enough differentiation.

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