detect_stack

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not explain how the stack is inferred, what the output format is (beyond an output schema existing), or any edge cases like empty file lists. The description is generic and lacks insight into the tool's 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?

The description is a single, focused sentence that is front-loaded with the core action. It contains no extraneous information and is appropriately sized for the tool's simplicity.

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?

Despite having one parameter and an output schema, the description provides minimal context. It lacks any guidance on when to use the tool relative to siblings, what constitutes 'dominant,' or any limitations. For an Agent, this is insufficient for confident tool selection, especially with no annotations to fill gaps.

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?

The schema defines 'files' as an array of strings with no description, and the overall schema coverage is 0%. The description adds the semantic that these strings are 'file paths,' which clarifies the parameter's purpose. However, it does not specify path types, constraints (e.g., non-empty), or how the array is interpreted, leaving some ambiguity.

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 the tool infers the dominant technology stack from file paths, using a specific verb ('infer') and resource ('technology stack'). It distinguishes itself from siblings like extract_api_contract and sql_to_flyway by focusing on stack detection rather than contract extraction or migration conversion.

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?

No guidance is provided on when to use this tool versus alternatives, nor are any exclusions or prerequisites mentioned. The single-sentence description implies usage only through its function, leaving the agent to infer context.

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