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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds substantive context beyond that: the verdict's provenance (copied from SecurityReportV1) and a semantic scope constraint about chain_id=1 versus fetchhub-4. It stops short of describing the shape or freshness of the returned verdict.

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: the purpose is front-loaded, followed immediately by the scope/provenance caveat and the exclusion. Every clause carries information an agent needs.

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 input parameters, no output schema, and annotations covering safety, the definition supplies the essential missing pieces: what the value represents and where it applies. The main remaining gap is that the returned "status" or "verdict" is never characterized (possible values, freshness), which the absent output schema would otherwise have covered.

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 tool takes zero parameters, so there is no parameter semantics to document; this is the baseline case for a well-formed no-arg tool. The description appropriately spends its space on scope and provenance instead.

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 and resource ("Return FET112's current machine-facing network status") and pins the scope to configured Fetch/ASI contracts on Ethereum chain_id=1. It also clarifies the data is derived from SecurityReportV1, which partially distinguishes it from siblings like fet112.security_report, though it never explicitly names which sibling to use for other cases.

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?

Provides a clear scope boundary with "Do not apply it to native fetchhub-4 traffic," which is an explicit when-not condition an agent can act on. However, it does not name the alternative tool to use for fetchhub-4 traffic or for non-configured contracts, leaving the routing inference to the agent.

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