fittin_invention

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is an external proprietary system and operates solely on the user's description. However, it does not describe side effects, failure modes, or limitations, leaving some behavioral gaps.

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 and use cases, and is well-structured. It is slightly verbose but each sentence adds value. Could be more concise without losing clarity.

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 single parameter and no output schema, the description adequately explains the tool's output (structured disclosure with novel elements, claim candidates, prior art) and its external nature. It is complete for the tool's complexity.

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 a detailed parameter description already provided. The tool description adds context about the tool's purpose but does not enhance parameter meaning beyond what the schema states. Baseline 3 is appropriate.

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 it generates a structured invention disclosure for IP protection, listing specific use cases (document invention, identify novel methods, etc.). The verb 'generates' and resource 'invention disclosure' are clear, and while sibling differentiation is not explicit, the purpose is distinct enough from sibling 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 a clear list of when to use the tool (e.g., 'document what they invented') and mentions it's a specialized external system. It lacks explicit when-not-to-use guidance or direct comparison to siblings, but the usage contexts are well-defined.

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