whats_new

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

No annotations are provided, so the description carries the full burden. It reveals the ordering ('newest first') but does not disclose any other behavioral traits such as whether pagination is supported (aside from the limit parameter), what fields are returned, or whether results include usage/security details. This is a minimal disclosure for a non-trivial list endpoint.

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?

Two sentences, front-loaded with the core action and ordering, then a brief usage example. No redundancy or filler; every word earns its place.

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?

The tool is simple with two optional parameters and no output schema. The description conveys the item type (AI agent tools), the source (SkillsIndex), and the ordering. It lacks a description of the return shape but the overall purpose is complete enough for a basic list endpoint given the schema covers parameter semantics.

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 already provides 100% coverage with descriptions for both parameters (limit and ecosystem). The description adds no additional context about how these parameters behave or interact, so it neither enhances nor detracts from the schema. Baseline 3 is appropriate.

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 returns most recently added AI agent tools, sorted newest first. It uses a specific verb ('Get') and resource ('AI agent tools on SkillsIndex'), and distinguishes itself from sibling tools like search_tools and get_top_rated.

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 explicitly tells the user when to use this tool ('to discover fresh MCP servers, skills, and tools the directory just indexed'). It does not mention when not to use it or explicitly name alternatives, but the use case is clear enough for an agent to make a basic selection decision.

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