stt_research

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

No annotations are provided, so the description must carry the burden. It only states return structure but does not disclose behavioral traits like read-only nature, authentication needs, rate limits, or whether it modifies data. This is insufficient for a tool that may have side effects.

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 two sentences long, no filler, and front-loads the action and result. Every word contributes to understanding.

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 tool's simplicity (one parameter, no output schema, no annotations), the description covers the core functionality and return structure adequately. It could mention the scope (e.g., Shopify product data) but is largely complete.

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?

The schema has 0% description coverage for the only parameter (keyword). The description adds that the keyword is a 'niche/keyword', which is minimal but clarifies the input role. It does not specify format, allowed values, or constraints beyond the required flag.

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 purpose: search a specific resource (Sell The Trend NEXUS) for a niche/keyword and return structured product data. It distinguishes from siblings like stt_search_products by emphasizing 'winning-product data' and structured output.

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 implies usage for pulling winning-product data, but does not explicitly state when not to use it or compare to alternatives like stt_winning_products or stt_search_products. The guidance is clear but lacks exclusion criteria.

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