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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, and the description adds cost/auth context: 'free, keyless, moves no money, nothing to sign.' It also clarifies the semantic boundary that a contract is not activation, payment, or outcome. Some repetition of 'read-only' keeps it from a 5.

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?

The core purpose is front-loaded, but the description is a long run-on list of every returned facet and then repeats 'free, keyless' in two consecutive sentences. With an output schema already present, that enumeration is largely redundant and should have been tightened.

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?

Given a one-parameter read-only tool with rich annotations and an output schema, the description gives enough context about scope, safety, and the evidence-ladder caveat to call it correctly. It could be improved by naming net_programs as the source of ids, but that is already in the schema.

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 the single 'id' parameter is already documented with its source in net_programs and an example. The description adds no further meaning about the id format or constraints, so baseline 3 applies.

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 specific resource ('One NET demand mechanism') and enumerates the contract facets returned, so an agent knows it retrieves full details for a single mechanism. It does not explicitly contrast itself with sibling tools such as net_programs or net_review_evidence, keeping it below 5.

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?

It implies usage by saying it returns the mechanism 'in full' and warns that a contract is not activation, adoption, payment, or an outcome, which sets a when-not boundary. However, it names no alternatives and gives no explicit routing guidance, so an agent must infer when to choose it over related tools.

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