IndieStack

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

Annotations only provide readOnlyHint=false; description adds significant behavioral context including auth requirements ('No API key required'), performance ('Takes 1 second'), and data lifecycle ('tools with high success rates get recommended more'). Could be improved with rate limit or idempotency details.

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?

Information is front-loaded with purpose and importance, followed by technical details. The Args section efficiently documents parameters. Minor deduction for slight verbosity in persuasive language ('Every report builds...'), though justified given the tool's reliance on agent participation.

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?

Comprehensive for a 5-parameter tool with output schema present (no need to describe returns). Covers all parameters, explains ecosystem impact (cross-agent data), integration context (IndieStack), and distinguishes required vs optional fields through description text.

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?

With 0% schema description coverage, the description fully compensates via the Args section, providing semantic meaning for all 5 parameters including format specifications (e.g., 'comma-separated slugs') and purpose context ('Records a verified stack') that the schema lacks.

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?

Description opens with specific verb 'Report' and resource 'whether a recommended tool worked', clearly distinguishing this as a feedback/reporting mechanism distinct from sibling tools like 'recommend' or 'check_compatibility'. The scope (improving future recommendations via outcome data) is explicitly stated.

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 directive ('ALWAYS call this after helping a user integrate an IndieStack tool') and emphasizes urgency ('single most valuable action'). However, lacks explicit when-NOT-to-use guidance or named alternatives to avoid confusion with 'report_compatibility'.

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