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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds context about data sources and return fields, but does not disclose potential caveats such as data latency, completeness limitations, or external API dependency. No contradiction with annotations.

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 concise and front-loaded with the target user and core purpose. The keyword list at the end is slightly redundant but does not detract significantly. Each sentence contributes meaning.

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 a read-only lookup tool with rich annotations and 100% schema coverage, the description provides sufficient context: what it does, who it's for, input approach, and output contents. It is functionally complete, though a note on result size or pagination would strengthen it.

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 parameters are already well-documented. The description restates that employeeName or employeeId can be used and mentions companyName for assignment checking, but adds little beyond the schema. 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 clearly states the tool tracks employee patent filings and flags unassigned inventions, specifying the data sources (USPTO/WIPO) and output (assignment status, filing dates, ownership gaps). This is specific and actionable, though it does not explicitly differentiate from sibling tools like patent_ownership_audit.

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 mentions use cases ('IP audits, inventor onboarding, compliance checks') and target audience (CHROs), providing some context. However, it lacks explicit guidance on when not to use this tool versus alternatives, and no sibling tools are referenced.

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