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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds that it returns 'structured data with clause types, risk levels, and relevant legal context,' which is useful. However, the mention of 'Sources: USPTO PatFT and EPO Espacenet public datasets' is misleading for a tool that analyzes contract text, creating confusion about its data dependencies and possibly implying it searches patent databases.

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 the core purpose, but it includes a 'Keywords' list at the end that is unnecessary for an AI agent and appears SEO-oriented. The 'Sources' line is also questionable and adds clutter. While not excessively long, these extraneous elements reduce overall conciseness.

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?

The presence of an output schema means the description does not need to explain return values. The description covers the main use cases and purpose, while the schema handles parameter details. However, the confusing source reference slightly detracts from completeness, as it might mislead the agent about the tool's data inputs, but overall the information is sufficient for correct selection and invocation.

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 all parameters already have descriptions in the schema. The tool description does not add meaningful parameter semantics beyond what is already documented; it only implicitly aligns 'contractText' with 'analyzes employment contract text' and 'legal context' with includeContext. No additional syntax or format details are provided, so the baseline of 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 a specific verb and resource: 'analyzes employment contract text to identify and extract IP-related clauses.' It lists specific clause types (invention assignment, confidentiality, non-compete, patent rights) which distinct it from generic legal clause extractors. The CHRO-targeted scope further clarifies its specialized purpose.

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 clear use contexts: 'Ideal for contract review workflows, compliance checks, and IP protection strategy.' It does not explicitly mention alternatives or exclusions, but the IP-specific focus implies when it should be preferred over more general tools like legal_clause_extractor. The 'For CHRO use' adds audience guidance, though no explicit 'when not to use' is given.

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