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

With no annotations, the description carries the full disclosure burden and delivers: submissions are 'staged for review, not immediately added to the live feed', and inclusion is only 'possible', not guaranteed. It also discloses the auth prerequisite and the x402 exclusion. It stops short of describing response format or rejection outcomes, but the most decision-relevant behavioral traits are covered.

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?

Three sentences, each earning its place: purpose in sentence one, auth/access constraint in sentence two, staging behavior in sentence three. The most critical facts are front-loaded before constraints, with zero fluff.

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?

With no output schema and no annotations, the description wisely explains post-submission behavior (staged, not live) and the auth path, which are the essentials for calling a submission tool correctly. The one notable gap is the absence of valid indicator_type values, a schema deficiency the description could have patched.

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 60% — confidence, source_note, and malware_family are documented in the schema, but the two required parameters (indicator, indicator_type) lack descriptions. The description's phrase 'observed indicator' adds only situational context and gives no format guidance for indicator_type values. It neither meaningfully compensates for the gap nor makes it worse.

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 ('submit'), a resource ('an observed indicator'), and a clear outcome ('validation and possible inclusion in future query results'). The domain framing ('PG1 Sovereign Threat Intelligence') plus the submit-vs-get contrast against all nine sibling tools makes the tool's role unambiguous.

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?

Gives a clear use case — submitting an observed indicator for validation — and explicit operating constraints (Gumroad license key required, NOT available via per-query x402). It never names an alternative or says when not to use it; the contrast with the read-only get_* siblings is implied rather than stated.

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