netintel_domain_due_diligence

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

With no annotations, the description carries the full behavioral burden. It usefully discloses execution behavior — the three lookups run 'concurrently' and it handles failures 'with graceful…' (presumably degradation/fallback), which is meaningful for a fan-out aggregator. However, it omits auth requirements, rate limits, latency expectations, and how partial results are surfaced, and the text is truncated mid-disclosure.

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 dense sentence with the value proposition front-loaded and zero filler. It is slightly penalized because the text appears truncated ('with graceful…'), leaving an unfinished clause rather than a complete thought.

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 multi-source aggregator with no output schema and no annotations, the description should say more about what the 'acquisition brief' contains and how the heuristic appraisal and partial-failure handling work. It conveys the concept adequately but leaves the agent guessing at return shape and failure semantics.

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% and the description says nothing about the single 'domain' parameter — no expected format (bare domain vs URL vs with TLD), normalization behavior, or validation. The name is largely self-evident, but the description adds no meaning beyond the 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?

The description states a concrete composite action: combining domain availability, heuristic value appraisal, and TLD pricing into a single acquisition brief. This implicitly routes the agent away from the single-purpose siblings (netintel_domain_availability, netintel_domain_appraise, netintel_tld_price) toward the all-in-one call. It is clear but does not name those siblings explicitly.

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?

Usage is implied rather than stated: 'One call combines...' suggests this is preferred when the agent wants availability, value, and pricing together, versus making three separate calls. There is no explicit when-to-use/when-not guidance and no mention of the tradeoff (extra latency/cost of fan-out) against the individual tools.

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