Newly added tools

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

No annotations are provided, but the description sufficiently discloses that this is a read-only operation returning a list of recent tools with specific fields and a limit parameter. It does not discuss error handling or rate limits, but for a simple list tool, this is adequate.

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 sentence that clearly and efficiently conveys the tool's function, return format, and default ordering. No unnecessary words.

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 simplicity of the tool (optional parameter, no output schema), the description is mostly complete. It could explicitly mention the default limit of 25, but the schema covers that. No missing critical information.

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 description coverage is 100% for the single parameter `limit`, which includes its purpose, default, and max value. The description adds no additional meaning beyond what the schema already 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 it returns the most recently added tools, ordered newest first, and specifies the fields included (slug, name, URL, description). It distinguishes from sibling tools like get_tool (single tool) and search_tools (search).

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 listing new tools but does not explicitly state when to use this tool versus alternatives like browse_category or search_catalog. No exclusions or alternative recommendations are provided.

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