netintel_tech_fingerprint

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

No annotations are provided, so the description carries the burden. It discloses the evidence sources (HTTP headers and HTML), which explains methodology, but says nothing about auth requirements, rate limits, failure modes, or whether the target site must be publicly reachable.

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?

A single, front-loaded sentence that names the action, target, categories detected, and the data sources. No filler.

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?

For a single-param detection tool with no annotations and no output schema, the description covers what is detected and how, but omits return structure (e.g., keyed categories), failure behavior, and any constraints. Adequate but with clear 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?

Only one parameter (url) with 0% schema description coverage. The description implies the url points to a website to profile, but doesn't clarify format expectations (scheme required, subdomain handling, etc.). Baseline 3 for a single-param tool with no schema detail.

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?

States a specific verb (Detect) and resource (full technology stack of a website) and enumerates the categories it covers (CMS, framework, CDN, analytics, security tools). This clearly distinguishes it from siblings like netintel_cloud_fingerprint and netintel_web_fetch.

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?

The description implies the use case (profiling a website's tech stack) but doesn't explicitly state when to use this versus netintel_cloud_fingerprint, netintel_page_extract, or netintel_schema_parse. No exclusions or prerequisites are given.

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