legal_tm_opposition_draft

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

No annotations are present, so the description must disclose behavioral traits. It only mentions routing under JWT/tenant/company scope and fails to describe side effects (e.g., creating or modifying opposition drafts), permissions required, or rate limits. The description adds minimal behavioral context beyond what is obvious.

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 concise (under 50 words) with front-loaded purpose and clear parameter listings. Every sentence serves a purpose, though the technical routing detail could be condensed.

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?

Although an output schema exists, the description does not mention return values, error conditions, or expected behavior. For a domain agent action that likely generates a draft, this omission leaves the agent unaware of what to expect from the invocation.

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 0% schema description coverage, the description adequately explains both parameters: message is a free-text objective, inputs is an optional JSON string of structured inputs. This adds meaningful context beyond the schema's basic type/title.

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 specifies the verb 'Run' and the resource 'legal domain agent action `tm_opposition_draft`', which is clear and distinct from siblings like `legal_tm_clearance_search`. However, it does not explain what 'tm_opposition_draft' actually does (e.g., draft a trademark opposition), relying on the tool name's domain knowledge.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios, prerequisites, or which sibling tools to prefer for related tasks.

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