get_network_map

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

No annotations provided; description discloses it's a read-only extraction tool. Lacks details on performance, limitations, or whether it handles duplicates, but adequate for a simple scanning tool.

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?

Two sentences with no filler. Purpose is front-loaded. Every sentence adds value.

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?

No output schema exists, but the description implies the output (list of URLs/services). For a simple extraction tool with one optional param, it is largely complete, though output format is not specified.

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 coverage is 100% and describes the 'scope' parameter. The description adds no extra parameter information, missing an opportunity to explain how scope affects results.

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 the tool extracts hardcoded URLs, API base URLs, and proxy patterns from Lampa source. The verb 'extract/reveal' and specific resource naming distinguish it from sibling tools like find_api_calls or find_files.

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?

Implies usage for discovering external services but provides no explicit guidance on when to use vs alternatives or when not to use. Among many siblings, more clarity would be helpful.

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