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

The description goes beyond what the annotations provide by documenting critical behavioral traits. Specifically, it informs the user that 'Missing and null fields remain unchanged' and that 'monetary values retain their original unit and runtime type,' which is crucial for downstream processing.

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 definition is extremely concise, using only two sentences. Both sentences are highly efficient, defining the resource contents and specifying data integrity rules.

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 complexity of retrieving business records, the description is highly complete. It details exactly which fields are documented and provides explicit instructions on how missing data is handled.

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?

Since the input schema coverage is 100%, the baseline score of 3 is appropriate. The description focuses on the data output rather than adding functional semantic meaning to the required inputs like `id` or `country`.

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's function: to 'Provider business records for TikTok Product Related Lives.' It precisely defines the resource and action, helping an agent select this over general search or detail tools.

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?

While it doesn't explicitly compare it to alternatives, the highly specific phrase 'Product Related Lives' in both the name and description provides strong context for when this tool should be used. It is highly targeted toward a specific data set rather than a broad query.

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