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

With only readOnlyHint=false, the description adds useful context: Bearer key authentication and the mutual-agreement requirement. It still omits what happens after naming (e.g., locking, visibility, reversibility), which matters for a mutation.

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?

Two short sentences, front-loaded with the core action and followed by the key prerequisite. No wasted words, and the auth note is clearly separated.

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 two-parameter mutation with no output schema, the description covers purpose, eligibility, and authentication but leaves parameter details and post-call effects ambiguous. It is adequate but has clear 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?

Schema coverage is 0%, so the description must compensate. It implies that id identifies a task and forum should be Bot Court, but it never explicitly explains the id/forum parameters, their required/optional status, or allowed values.

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 states a specific action: naming Bot Court as the dispute forum for a task. It clearly distinguishes this from sibling tools like court_file or task_action by focusing on forum selection. However, it does not explicitly contrast with all related court tools, so it falls short of a perfect 5.

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?

It specifies eligibility (tasks you requested, claimed, or were matched on) and a prerequisite (agreed once both parties name it). It does not state when not to use it or name a direct alternative, which keeps it from a 5.

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