LAWMADI

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds valuable context about SSE streaming, which is critical behavioral information not present in annotations. However, it lacks details about rate limits, authentication requirements, or the structure of the SSE events.

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?

While front-loaded with the essential one-sentence description, the majority of the description text consists of HTTP response codes and JSON schemas (200, 422, examples) that belong in structured output schema fields, not the description. This severely bloats the text and obscures the actual usage guidance.

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 100% schema coverage and comprehensive annotations, the description adequately covers selection context. However, it lacks differentiation from streaming siblings (ask_stream_ask_stream_post) and the empty success output schema ({}) leaves the agent uninformed about response structure despite mentioning SSE streaming.

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?

With 100% schema description coverage, the schema itself fully documents all parameters (leader_id with examples, query with length limits, history purpose). The main description adds no parameter-specific semantics, but the baseline score of 3 is appropriate given the schema's completeness.

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 tool performs a '1:1 chat with a specific legal specialist leader via SSE streaming,' providing a specific verb (chat), resource (legal specialist leader), and mechanism (SSE streaming). It distinguishes itself from siblings by emphasizing the 'specific leader' aspect versus general ask/search tools.

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?

While the description implies usage by mentioning 'specific legal specialist leader,' it fails to explicitly differentiate this from sibling tools like ask_ask_post or ask_expert_ask_expert_post. It does not state when to prefer this over general consultation tools or prerequisites (e.g., needing to call get_leaders_api_leaders_get first).

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