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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds behavioral context by specifying the return value: 'Returns the thread link and public URL if the thread is public.' This clarifies the conditional nature of the public URL, going beyond the annotation defaults.

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 two concise sentences, front-loaded with the verb and resource, followed by return-value detail. Every word earns its place, with no filler or repetition.

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 simple read-only tool with one parameter, complete schema coverage, and an output schema, the description is fully sufficient. It states what the tool does, what it returns, and the public/private condition, leaving no critical gaps.

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 input schema provides 100% coverage for the single parameter 'session_id' with a clear description. The tool description adds minimal extra meaning, only positioning the session as 'previous debate session.' Since schema coverage is complete, a baseline of 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 clearly states the tool's purpose: 'Get the dashboard URL for a previous debate session.' It names a specific verb ('Get') and resource ('dashboard URL'), and distinguishes it from sibling tools like 'get-session' by focusing on link retrieval rather than general session data.

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 implies usage: it is for retrieving a link to a previous debate session. However, it does not explicitly state when to prefer this over alternatives like 'get-session', nor does it mention any conditions or exclusions beyond noting the public URL is returned only if the thread is public.

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