test_integration

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses that no secrets are returned, which is important, but it does not state whether it is a read-only operation, whether it makes network calls, or what happens if credentials are invalid. The absence of annotations is partially compensated by the 'no secrets returned' note, but other behavioral aspects remain unclear.

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, compact sentence that front-loads the core action and includes a critical qualifier ('no secrets returned'). Every word adds value, with no unnecessary filler or redundancy.

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 simple (one required parameter, no output schema), so the description covers the primary purpose. However, it lacks details about the return format, success/failure signals, and any side effects. For a verification tool with no annotations, this is a borderline acceptable but not fully complete definition.

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 description coverage is 0% for the 'provider' parameter. The description mentions 'for a provider' but does not explain what the parameter expects (e.g., valid values, format, requiredness). Since the schema offers no help and the description adds almost no parameter-specific guidance, this is a significant gap.

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 states a specific verb ('Verify'), a clear resource ('stored ATS credentials'), and a scope ('for a provider'), while also noting that no secrets are returned. This clearly differentiates it from sibling tools like list_integrations and get_integration_connect_url, which have different purposes.

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 implies a use case—verifying stored ATS credentials—but does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions. There is no reference to compared tools or conditions. The guidance is adequate for a simple verification but lacks explicit routing.

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