nexo_skill_featured

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

No annotations are provided, so the description carries the burden. It states the tool returns skills (implying a read operation), but does not disclose any behavioral traits such as authentication requirements, rate limits, or error conditions. It is minimally transparent but not fully informative.

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, clear sentence that efficiently conveys the tool's purpose. No unnecessary words, and it is appropriately front-loaded.

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 low complexity (one optional parameter, no output schema, no nested objects), the description is reasonably complete. It explains the purpose and context. Could mention the limit parameter or what 'featured' means, but overall adequate.

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 input schema has one parameter (limit) with 0% description coverage. The parameter name 'limit' is self-explanatory for limiting results, and the default is 5. However, the description does not mention the parameter at all, failing to add context beyond the schema. The bar is raised due to low coverage, but the simplicity keeps it at a 3.

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 it returns 'featured published/stable skills' for 'startup discovery'. The verb 'return' and resource 'skills' are specific. It distinguishes itself from sibling tools like nexo_skill_list (likely all skills) and nexo_skill_get (single skill) by specifying 'featured' and 'startup discovery', though 'featured' could be more explicit.

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 provides a context ('for startup discovery') but does not give explicit guidance on when to use this tool versus alternatives (e.g., nexo_skill_list, nexo_skill_match). No when-not-to-use or exclusions are mentioned.

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