IndieStack

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

Annotations indicate readOnlyHint=true, confirming this is a safe read operation. The description adds valuable behavioral context beyond annotations: it discloses the output structure ('compatibility matrix' with three specific states: verified, unknown, conflict), input constraints ('2-8 tool slugs'), and sequencing recommendations (calling check_health after). It could improve by mentioning rate limits or caching behavior.

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 purpose upfront, followed by usage context, specific constraints, workflow guidance, and finally parameter details. No redundant sentences; the 'Args' section efficiently documents the single parameter without unnecessary verbosity.

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 presence of an output schema, the description appropriately summarizes return values (the three matrix categories) without duplicating schema details. It covers the single parameter thoroughly despite sparse schema documentation. Minor gap: does not mention error handling for invalid slugs or out-of-range tool counts.

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 by providing the parameter format ('Comma-separated tool slugs'), a concrete example ('next-auth,prisma,stripe'), and quantity constraints ('2-8'). It does not explicitly describe the parameter as required, though this is visible in the schema's required array.

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 a specific verb ('Check') and clear resource ('whether a set of tools are compatible'). It distinguishes from siblings by explicitly directing users to 'Call check_health() afterward for maintenance status,' clarifying this tool handles compatibility matrices while check_health handles maintenance status.

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?

Explicitly states when to use ('validate a stack before recommending it', 'Ideal for always-on agents auditing dependency trees') and provides workflow integration ('Call check_health() afterward'). Also includes operational constraints ('Pass 2-8 tool slugs') that define valid usage boundaries.

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