IndieStack

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

Annotations declare readOnlyHint=true. Description adds valuable behavioral context beyond annotations: specifies output format ('crisp side-by-side table'), lists compared attributes (price, source type, upvotes, ratings, ejectable flag), and notes it provides a recommendation. Could improve by mentioning if results are cached or real-time.

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 and front-loaded: starts with purpose, urgency ('IMMEDIATELY'), value proposition ('Cuts decision time'), data coverage, then params. Every sentence earns its place. Minor deduction for informal 'Args:' section embedding param docs, though necessary given empty schema descriptions.

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?

Appropriately complete given output schema exists. Description wisely focuses on comparison semantics and trigger conditions rather than return structure. Lists all compared fields comprehensively. Could mention return type (table vs JSON) but sufficient for agent selection.

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 has 0% description coverage (only titles 'Slug A/B'). Description fully compensates by specifying these are 'URL slugs' and providing concrete examples ('plausible-analytics', 'simple-analytics'). Clarifies ordinal relationship ('First tool', 'Second tool'). Slight deduction for not mentioning format constraints (kebab-case, etc.).

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?

Clear specific verb ('Compare') + resource ('IndieStack tools') + scope ('side by side'). Explicitly distinguishes from sibling get_tool_details by contrasting with 'reading two separate tool details' and establishes relationship with find_tools as the trigger.

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?

Excellent explicit guidance: 'Call this IMMEDIATELY when find_tools() returns 2+ plausible options.' Defines precise trigger condition (user hasn't committed) and implicit alternative workflow (don't use for single tools). Mentions sibling find_tools by name as prerequisite.

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