get_patent_brief

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

No annotations are supplied, so the description carries the full behavioral burden. It specifies truncation semantics ('the first item that does not fit ends the brief'), that 'truncated and omitted say what was left out', the token-counting proxy and guarantee 'never over max_tokens', plus anchor/quote conventions and the GET endpoint. That is unusually complete for a read tool; only auth and error cases are absent, which are secondary here.

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 front-loaded with purpose, but it is a dense single paragraph with semicolon-delimited clauses that is hard to scan. Some response-format detail is redundant because an output schema exists, though most sentences still carry useful behavioral information.

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 has an output schema, so return shape need not be explained, yet the description adds important truncation and token-budget behavior. Missing patent_id format guidance and error behavior keep it from being fully complete for a two-parameter retrieval tool.

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 gives max_tokens range, default, and tokenizer proxy, and shows patent_id in the endpoint path, but it does not state accepted patent_id formats. That is meaningful compensation with one clear gap.

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 resource and scope: a token-limited brief of one US patent, including status, claims, and term keys. It is clear what the tool does, but it never names or differentiates itself from siblings such as get_claim_tree or check_patent_status.

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?

Usage is implied by the emphasis on fitting max_tokens and the brief format, but there is no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent can infer it is for compact patent summaries under a token budget, but must decide against siblings on its own.

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