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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this is not a read-only operation, but the description adds no behavioral context whatsoever—no indication that this is a ranked product listing, what time windows mean, whether results are paginated, or what authentication is required. For a 34-parameter data tool, the description carries almost none of the burden the sparse annotations leave.

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?

It is short, but short because it is under-specified rather than economical—a single fragment that restates the title. No sentence earns its place by adding information.

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 tool with 34 parameters, no output schema, and a sibling with a nearly identical name, the description provides nothing to help an agent orient itself. It is completely inadequate relative to the complexity of the tool.

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 34 parameters are documented in the schema itself; the description adds no parameter meaning beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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 is essentially a restatement of the tool name/title ('1688 Sourcing: product Billboard API') and never says what a 'billboard' is, what data it returns, or what operation it performs. It does not distinguish this tool from the near-identical sibling nexscope_1688_product_billboard, leaving the agent unable to tell them apart.

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?

No guidance is given on when to use this tool, when not to, or which sibling (e.g., nexscope_1688_product_billboard or nexscope_1688_product_search) to choose instead. The agent must infer usage entirely from the parameter schema.

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