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

Annotations already declare openWorldHint=false, destructiveHint=false and, notably, readOnlyHint=false, so the safety profile is structured rather than described. The description adds nothing beyond that — no cost/rate-limit info, no auth requirements, no error or empty-result behavior — and the word 'lookup' reads like a pure read while readOnlyHint is false, a mild tension the text never resolves.

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?

One short, front-loaded sentence with no filler or redundancy. Brevity here reflects under-specification rather than bloated prose, so the structure itself is fine.

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 an undocumented required parameter, no output schema, and no readable annotations, one sentence is not enough for an agent to call it confidently. At minimum the expected format of 'tech' and the shape of the JSON result should be hinted at.

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 single required parameter 'tech' has 0% schema description coverage and the description supplies no meaning for it. It is unclear whether 'tech' expects a technology name, a keyword string, a slug, or a domain-style token, so the schema gap is not compensated anywhere.

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 resource (technology trend data) and implies a read-style JSON retrieval, so the general intent is graspable. But it never says what a 'trend' actually is here — time series, search volume history, adoption curve — and it does nothing to separate itself from adjacent siblings such as keywords-api or domain-api. Purpose is vague rather than tautological.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for a related question. With roughly thirty sibling *-api tools in the catalog, the absence of any routing guidance leaves the agent to guess.

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