Find Emerging Skills

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

Annotations declare readOnlyHint=true, and the description adds rich behavioral detail: it tracks 'companyCount across the last 3 monthly snapshots', 'non-decreasing' growth from a low base, meaningful absolute gain, and returns a 'deliberately tight list'. No contradictions.

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 a single paragraph, concise and front-loaded with the purpose. It is slightly dense but every sentence adds value. Minor improvement could be clearer separation of usage details.

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 6 parameters and no output schema, the description explains the algorithm and expected behavior well. It mentions return is a 'tight list' and how to widen. Could hint at output fields, but overall sufficient given context.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the rationale behind each parameter (e.g., minDelta filters small-base noise, adoptionMax excludes mainstream) and interprets default values, going beyond what the schema alone provides.

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 finds skills with 'low-but-consistently-growing market adoption' and specifies it's for 'early-stage signals'. The verb 'find' and resource 'emerging skills' are explicit, and the description distinguishes from sibling tools by focusing on emerging trends.

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?

Provides explicit use cases: 'what skills are quietly trending?' or 'what should I learn before everyone else?'. It also explains how to adjust parameters to widen results. Missing explicit when-not-to-use or alternatives, but context is clear.

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