bidirectional_citation_graph

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

With no annotations, the description carries the full burden, and it does disclose the internal pipeline (Google Patents search, then forward and backward citation fetches, optional competitor matrix). It does not state that the operation is read-only, that it performs many sequential network calls with associated latency/cost, or how partial failures are handled. Adequate but incomplete for a multi-step network tool.

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?

Three short sentences, front-loaded with the purpose, then the mechanism, then the conditional branch and return fields. No sentence is redundant and nothing is buried.

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?

There is no output schema or annotations, and the description compensates by listing the returned artifacts (patents list, forward_graph, backward_graph, competitor_matrix). All three parameters are documented and the conditional path is explained, though operational caveats like latency and read-only behavior are absent.

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 baseline is 3, but the description adds real semantics beyond the schema by explaining that competitor_keywords triggers an additional competitor citation matrix. It also implies the graph scope is bounded by the company's core patents, complementing the limit 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 gives a specific verb+resource ('Build full bidirectional citation graph') and immediately scopes it to a company's core patents. The word 'bidirectional' cleanly distinguishes it from the directional siblings get_cited_by and batch_get_cited_by, and the mention of the competitor matrix separates it from competitor_citation_matrix.

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 states the conditional trigger for one behavior ('If competitor_keywords provided, also runs competitor citation matrix'), which is useful. However, it never says when to choose this tool over get_cited_by, batch_get_cited_by, or competitor_citation_matrix, so usage relative to alternatives is only implied.

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