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

Annotations declare this is a non-read-only, open-world, non-destructive write, and the description adds genuinely useful behavior beyond them: deduplication is keyed on patent_number (so repeat calls are idempotent), the call costs 5 credits, and an account is required. Missing only what happens on conflict (merge vs reject) and the return value.

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?

Four terse clauses, front-loaded with the action, then the requirement, then dedup, then cost/auth. Every sentence carries distinct information and nothing is padded.

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 an 11-parameter mutation tool with no output schema, the description covers the essentials an agent needs to invoke it correctly: the key required identifier, dedup semantics, cost, and auth requirement. It stops short of explaining output or edge-case behavior, but the annotations carry the safety profile.

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 73%, so most parameters are already documented in the schema (including the patent_number exemplar and the status enum-like list). The description only reiterates that patent_number is required and repeats its format, adding little beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Submit a patent record') that maps cleanly to the domain object, distinguishing it in substance from the many other submit_* siblings by resource type. However, it never names or contrasts with an alternative (e.g. 'for company/startup records use submit_startup'), so differentiation is left to inference from the noun.

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?

Gives a prerequisite ('Needs a free StartupHub.ai account') and an implied dedup rule, but never states when to use this tool versus the other ~10 submit_* siblings or when to skip submission (e.g. record already exists). No explicit when/when-not guidance.

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