osint_tech_stack

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

With no annotations at all, the description carries the full behavioral burden but reveals little beyond the category list: nothing about whether it fetches the live page or uses headers, whether the target must be publicly reachable, whether detection is passive, or whether it costs rate-limited requests. An agent cannot predict failure modes or side effects from this text.

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?

One front-loaded sentence that leads with the resource and ends with concrete examples, with no wasted clauses. The 'OSINT Tool:' prefix is mildly redundant given the tool namespace but costs little.

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?

An output schema exists, so return values need not be explained, and a one-parameter tool is low complexity. Still, for a live-fetch reconnaissance tool with zero annotations and zero schema coverage, the description should state at least URL format expectations and whether the target page must be reachable.

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 single required parameter 'url' has 0% schema description coverage, so the description must compensate and does not: it never says whether the URL needs a scheme, whether subpaths matter, or whether redirects are followed. The tech-stack categories mentioned describe output, not the input's expected format.

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 names a specific verb ('Fingerprint') and a concrete resource ('web technology stack'), then enumerates covered categories (frameworks, CMS, CDN, servers) with examples like React, Vue, Next.js. That is enough to separate it from neighbors such as osint_domain_recon, though it never explicitly contrasts itself with them.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as osint_domain_recon or scrape_url for overlapping reconnaissance needs. Usage is only inferable from the category list, not stated.

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