Run Session Verifier

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Run the Runtime-owned verifier', which implies execution but does not state whether the operation is read-only, mutating, what it validates, or what happens to session state. This is insufficient for an agent to anticipate 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 a single, concise sentence with no redundant words or filler. It is front-loaded with the action, though its brevity borders on under-specification, which slightly reduces its effectiveness as a standalone guide.

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?

This tool has no annotations, no output schema, and a minimal description. It fails to explain return values, error conditions, the verifier's behavior, or the meanings of two of three parameters, making it incomplete for a tool with nested objects and unclear operational details.

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 schema description covers only the handle parameter (33% coverage), and the tool description adds no information about lease_ttl_ms or operation_id. The description does not compensate for the missing schema explanations, leaving two parameters semantically ambiguous.

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 action ('Run') and a specific resource ('Runtime-owned verifier for the current AgentSession state'), distinguishing it from sibling session tools like begin/resume/turn. However, it does not clarify what 'verify' means or what the verifier checks, leaving some ambiguity about its exact purpose.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or alternative tools, so an agent lacks context for when verification is needed compared to other session operations.

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