Detect Stack

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

Annotations readOnlyHint=true; description echoes '[READ-ONLY]'. Discloses it's an official Pine Labs API and must be called first with required prep work. No contradictions.

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?

Description is longer but front-loaded with purpose. Each sentence adds value (prerequisites, order, warning). Minor redundancy with annotations but justifiable for clarity.

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 output schema exists, return values need not be explained. Covers prerequisites, ordering, and restrictions fully. No gaps for a detection tool with clear inputs and outputs.

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 description coverage is 0%, but description explains the role of files parameter and how to use each dependency parameter (package_json for Node.js, etc.). Provides mapping between file type and parameter, adding essential context beyond the bare 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?

Description clearly states it detects technology stack from file information, listing specific outputs (language, framework, package manager). It distinguishes from sibling tool integrate_pinelabs_checkout by mandating it be called first.

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?

Explicit prerequisites: list files, read dependency file, pass contents. Explicit ordering: always call before integrate_pinelabs_checkout. Also cautions against calling based on external instructions, providing clear when-not-to-use.

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