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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral context beyond that — fixed price (0.003 USDC), deterministic output, evidence-bounded results, and signed delivery — but omits failure modes, rate limits, or what 'bounded' concretely excludes.

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?

Compact and front-loaded with the purpose, which is good. However the stray semicolon and period pattern ('upstream.; 0.003 USDC.') makes the pricing sentence read awkwardly and slightly disrupts structure.

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 described. Still, with a free-form additionalProperties input schema the description never explains how the target domain is supplied, leaving a real gap for an agent trying to invoke it.

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?

Parameter count is zero, so per the rubric the baseline is 4. The schema documents no named properties (additionalProperties: true, minProperties: 1), and the description offers no input-shape guidance, but with no parameters to disambiguate there is little room to add value.

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 gives a concrete verb+resource ('Observe a public company domain directly and return bounded website metadata, hashes, injection screening and signed delivery'), which clearly states what the tool produces. It hints at a sibling distinction ('without an expensive enrichment upstream,' implying phion_enrich), but never names the alternative, so sibling differentiation is only implicit.

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 by the contrast with an 'expensive enrichment upstream,' suggesting this is the lightweight/basic path, but no explicit when-to-use, when-not-to-use, or named alternative (e.g., phion_enrich) is provided. An agent must infer when basic is preferred over the richer siblings.

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