UPC Intel

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

With no annotations provided, the description carries the full behavioral burden. It does disclose that the tool returns both counts and the decisions themselves, and that it computes no rates or scores. However, it does not state whether matching is exact or fuzzy (though the schema's 'partial judge name' hint covers this), what happens with no results, or that it is a read-only operation. It adds moderate value beyond the schema but lacks richer behavioral context.

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?

A single sentence with zero waste. The core purpose is front-loaded ('List the stored decisions...'), the return content is specified ('counts and the decisions themselves'), and the exclusion is stated ('no rates or scores are computed'). Every clause earns its place.

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 simple — one required parameter, no output schema, no annotations. The description covers what it does, what it returns, and what it excludes, which is largely sufficient for an agent to invoke it. Without an output schema, it appropriately explains the return shape. The only minor gap is the absence of explicit sibling differentiation, but that is already penalized under usage guidelines.

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 description coverage is 100%, so the schema already documents judge_name with an example ('Grabinski') and the partial-match semantics. The description adds no parameter-specific detail beyond the schema. Per the rubric, the baseline 3 applies when schema does the heavy lifting.

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 verb ('List'), a resource ('stored decisions'), and a scope ('in which a judge is recorded as presiding judge'). It clearly differentiates from siblings by focusing on judge-centric decisions rather than case details, patent proceedings, or docket searches. The exclusion 'no rates or scores are computed' adds precision about what the tool does not do.

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 context — call this when you want decisions for a presiding judge — but never explicitly states when to prefer it over alternatives or names any sibling. The 'no rates or scores are computed' line hints at a boundary (if you need scores, use something else), but no alternative is identified and no explicit when-to-use guidance is given.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that EPO data is included only where fetched, which is useful, but it doesn't state what the tool returns when EPO data wasn't fetched (empty array, null, or error), whether court decisions are returned in any particular order, or what the response shape looks like. This partial disclosure leaves meaningful ambiguity for a tool that combines two data sources.

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?

A single, efficient sentence delivers the core purpose upfront and the data-source nuance in a parenthetical. There is no wasted wording, and the main scoping phrase 'everything the database holds about one patent' leads the sentence. It could arguably break the two clauses into separate sentences for readability, but the current structure is compact and scannable.

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 one-parameter tool with 100% schema coverage and no output schema, the description covers the essential purpose and data sources well. The main gap is the unelaborated 'where fetched' condition; an agent must guess what happens for patents without fetched EPO data. Since this is the only notable omission in an otherwise clear definition, a 4 is warranted.

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 description coverage is 100%, with the single patent_number parameter fully documented including an example format ('EP3883351'). The description adds the context that this parameter selects a patent whose proceedings are retrieved, but it doesn't add technical detail beyond what the schema already provides. The baseline of 3 is appropriate for complete schema coverage.

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 uses a specific verb (Get) with a well-defined resource (everything the database holds about one patent) and enumerates the exact contents: EPO register status and events plus all stored court decisions involving it. The patent-specific scope clearly distinguishes it from siblings like get_case_details and get_judge_decisions.

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?

No explicit when-to-use guidance is provided. The description doesn't state when to prefer this tool over get_case_details, get_judge_decisions, or search_european_dockets. The distinction is only implicit in the word 'patent' versus the siblings' case/judge/docket focus, so an agent must infer the routing criteria. The conditional 'where fetched' hints at data availability but doesn't explain the scenario fully.

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