Chat with the published agent

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

No annotations are provided, so the description carries the full burden. It does disclose real behavior beyond the schema (return shape of replies/activities, the sign-in-card → signInUrl branch), but it is silent on auth requirements, the long-running/orphaning risk, and rate or timeout behavior that the agent would want to know.

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?

Three short sentences, front-loaded with purpose and then the continuation hint and the sign-in edge case. Every sentence carries information; the sign-in sentence is slightly peripheral but genuinely useful for a chat tool.

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 14-parameter tool with no annotations and no output schema, the description is thin: it never explains the authentication modes, defaults, or the background/jobId escape hatch that the schema also flags. It partially compensates by naming the response fields, but a caller still needs to open the schema to use it safely.

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 71%, so most parameters are already self-documented, including conversationId, whose description matches the sentence in the tool description. The description adds no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 gives a precise verb+resource pair ('Send one utterance to the published agent and return its replies') and clarifies the return surface with 'and raw activities'. It is clearly distinguishable from transcript/evaluation siblings on intent, though it never names an alternative explicitly.

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?

'Use conversationId to continue' is the only usage directive, which implies the multi-turn pattern but never states when to pick cs_chat over cs_run_conversation_tests or how to start a fresh vs. resumed conversation. Context is implied rather than argued.

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