legal_ip_docket_sync

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

The description mentions JWT/tenant/company scope and dispatcher routing, but does not disclose side effects. Given destructiveHint is true and readOnlyHint is false, users need more explicit warning about what mutating or destructive behavior `ip_docket_sync` may perform.

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 short sentences with no unnecessary fluff or repetition. It is well-structured and easy to scan.

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?

The tool is a generic dispatcher wrapper, but the description lacks essential context about the underlying IP docket sync action, its expected inputs, its outcomes, and any side effects. It is not complete enough for an agent to decide when or how to use it effectively.

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 schema provides no descriptions, so the description must carry the burden. It minimally clarifies that `message` is a free-text objective and `inputs` is an optional JSON string, but gives no concrete structure, examples, or semantics for either parameter.

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 generic verb ('Run') and names the action `ip_docket_sync`, but does not explain what an IP docket sync actually does or why it would be chosen. The added routing context does little to distinguish this tool from other legal-domain actions like legal_vendor_renew.

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?

There is no guidance on when to use this tool versus any alternative. The description only says it routes through a dispatcher, which is implementation detail rather than usage guidance.

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