patentpulse

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

With no annotations, the description adds pricing per endpoint and mentions coverage and multilingual capabilities. However, it lacks disclosure of rate limits, authentication requirements, or response format, which are important for behavioral transparency.

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 well-structured with a general overview followed by a bullet list of endpoints. However, it is verbose with repeated formatting and includes costs which may not be essential for agent selection. Could be more concise.

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?

Given the tool's complexity (16 parameters, multiple endpoints) and no output schema, the description covers the primary use cases and parameter purposes well. It lacks details on return values or pagination, but the endpoint descriptions provide sufficient context for selection.

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 100%, but the description adds meaningful context beyond schema, such as listing example values for 'drug' (humira, ozempic) and providing jurisdiction codes in the 'jurisdiction' parameter description. This helps the agent understand parameter usage.

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 explicitly states 'global IP intelligence' and lists numerous specific endpoints (e.g., USPTO/EPO patent search, FTO, SEP), clearly differentiating it from sibling 'pulse' tools which target other domains. The verb 'search, analyze' is implied through endpoint names.

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 detailed endpoint-specific guidance (e.g., 'global' for jurisdiction-specific search, 'fto' for freedom-to-operate) and includes contextual parameters like 'jurisdiction' and 'standard'. However, it does not explicitly exclude use cases or mention alternatives among siblings.

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