IndieStack

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

Annotations declare readOnlyHint=true confirming safe read operation. Description adds valuable behavioral context distinguishing this from relevance-based search, and explains pagination behavior in the Args section. Does not mention rate limits or caching, but covers primary behavioral traits.

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?

Well-structured with clear paragraph breaks: purpose, usage guidelines, sibling differentiation, then parameter details. Every sentence serves a distinct function; no redundancy. Front-loaded with the core action.

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 2-parameter read-only tool with existing output schema, the description is comprehensive. It handles sibling differentiation, usage contexts, and parameter documentation that the schema lacks. No critical gaps remain.

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 0% (properties lack descriptions), but description fully compensates via Args section documenting limit ('default 10, max 50') and offset ('Pagination offset... Use offset=10 to see the next page'), providing semantics, defaults, and usage guidance absent from schema.

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?

Opens with specific verb 'Browse' + resource 'recently added developer tools on IndieStack'. Explicitly distinguishes from sibling tool find_tools() by clarifying this returns 'newest arrivals across all categories, not ranked by relevance'.

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 when-to-use scenarios ('when the user asks what's new, what's trending, or wants to explore... without a specific need') and explicit fallback condition ('when find_tools() returns no results'). Names the alternative tool directly.

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