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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine non-annotation context: shares follow published tallies and agencies count families vs filings differently, so cross-source comparison needs care. That data-reliability caveat is exactly the kind of behavioral disclosure that helps an agent interpret results.

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 Purpose/Guidelines/Limits/Ex structure is front-loaded and each labeled line earns its place. The trailing 'Ex: get_6g_patent_landscape()' is mildly redundant, showing a zero-argument call that adds little beyond the name.

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?

With an output schema present, return values need not be described, and annotations cover the safety profile. The description supplies purpose, usage trigger, and a data caveat, leaving little an agent needs missing before calling 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% with documented keyword, language, and response_format parameters, so the schema carries the parameter burden. The description adds no parameter detail beyond that, which is the expected baseline when structured fields are complete.

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 names a specific resource (the 6G core patent landscape) and its breakdown dimensions (by country and by company), which is far more precise than a tautology. The verb is nominal ('the landscape') rather than an explicit action verb, but the resource is unambiguous and no sibling covers patents, so routing is easy.

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 Guidelines line gives a clear trigger condition: 'use when a question needs the competitive patent picture.' It states when to use it but names no exclusions or alternative tools, which is forgivable since no sibling overlaps in the patent domain.

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