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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the check inspects recent runs and is meant to confirm data flow, which is useful framing, but says nothing about what a failed verification looks like or how results are returned.

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 tight sentences, zero filler, with the purpose front-loaded and the timing guidance second. Nothing to trim.

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 simple, read-only verification tool with no output schema, the description covers what it does, why, and when to call it. The one remaining gap is how an agent should interpret the verification result, but that is a minor omission given the tool's simplicity.

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 100% for the single optional promptName parameter, so the schema already carries the semantics and a 3 is the baseline. The description never mentions filtering by agent name, so it adds nothing beyond structured data here.

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?

States a specific verb and resource — 'verify that your Converra integration is working by checking recent runs' — which is concrete and actionable. It does not, however, differentiate itself from adjacent siblings like list_runs, get_agent_status, or list_integrations, so an agent must infer the boundary.

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?

Gives explicit triggering context: 'Run this after setting up the SDK or webhook to confirm data is flowing.' That is a clear when-to-use signal. It stops short of naming alternatives or stating when this tool is the wrong choice.

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