get_conversations

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

With no annotations, the description carries the burden and does useful work: it discloses the underlying HTTP verb (GET /openapi/v1/conversations/{app_id}), identifies the call as a read, and warns that it paginates 'up to a safety cap'. It stops short of stating auth needs or what happens at the cap.

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?

Front-loads the purpose in one line, then parameter meanings, then behavioral notes about the endpoint and pagination. Well-organized with no filler, though the Args block slightly restates what the parameter list already implies.

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?

An output schema exists, so return values need not be described. Given the low-complexity two-parameter read, the description covers purpose, parameters, read-only nature, and pagination behavior adequately; only auth/truncation semantics are left implicit.

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%, so the description must compensate and largely does: app_id is explained as the workspace/application id sourced from list_workspaces, and version is explained as optional with 'omit for the latest'. It could say more about the version value's meaning, but both parameters are given usable semantics.

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 (List) and resource (ADM conversations / observed talker pairs) scoped to a workspace. The parenthetical 'raw src→dst:port pairs ADM used to propose policy' distinguishes it from sibling flow-search tools like search_flows and top_risky_flows without needing their schemas.

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?

Usage is implied by the resource ('conversations for a workspace') and it helpfully points to list_workspaces as the source of app_id. However, it never states when to choose this over search_flows or other inventory/flow tools, and gives no exclusions.

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