test_integration

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

With no annotations, the description fully discloses behavior: for SN->external it touches a record and polls, for external->SN it POSTs a payload and verifies. It mentions 'harmless field' to indicate non-destructive side effect. Could add more on polling timeout or potential side effects.

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 well-structured with paragraphs for each direction and a list for return. It is relatively long but each section serves a purpose. Minor wordiness could be trimmed.

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?

Despite no output schema, the description explicitly states the return (pass/fail verdict, responses, correlation state). It covers both directions, all parameters, and the high-level flow. Complex tool needs this completeness.

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?

All 5 parameters have schema descriptions, and the description adds context: 'prefix' linked to design_integration plan, direction modes with clear usage, and conditional parameters explained per direction. This adds value beyond schema.

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 clearly identifies the tool's action (send test payload and verify) and the resource (bidirectional integration). It distinguishes between two directions and differentiates from sibling tools focused on other integration tasks.

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 explains when to use each direction and the required parameters based on direction. It does not explicitly state when not to use the tool or list alternatives, but the context is clear and adequate.

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