convergeqa_iterate_sessions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to indicate whether the tool is read-only, requires authentication, or any side effects. The minimal statement 'List owner-authenticated Iterate sessions' does not convey safety or mutability traits.

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 sentence, which is concise but likely too brief, sacrificing necessary detail for brevity. It is front-loaded with the verb, but important context about parameters and behavior is missing.

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 the tool has 6 parameters and no output schema, the description is severely incomplete. It does not explain what a session is, what output to expect, or how to use parameters. The agent has insufficient information to invoke the tool correctly.

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 50%, but the description adds no parameter details whatsoever. The schema already documents some parameters (base_url, api_key_env, service_account_key_env), but output, credential_kind, and redact_private_urls lack descriptions. The tool description does nothing to compensate for these gaps.

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 states the action ('List') and the resource ('owner-authenticated Iterate sessions'), which distinguishes it from the sibling tool 'convergeqa_iterate_session' (singular) that likely returns a single session. The term 'owner-authenticated' adds specificity but could be clearer.

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?

No guidance is provided on when to use this tool versus alternatives like 'convergeqa_iterate_session'. There is no discussion of prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone.

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