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

readOnlyHint=true already declares this is a safe read, so the bar is lower; the description does add a useful non-obvious constraint that no payment flow is triggered. It still says nothing about whether options are static or account-specific, or what a result looks like, and there is no output schema to fall back on.

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 short sentence with the purpose up front and no filler. It is arguably too terse rather than too long, but every clause present earns its place.

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 schema surface and no output schema, the description carries the burden of explaining what comes back, and it does not — 'options' could be a list, a policy document, or a config object. The read-only annotation covers safety, leaving the return shape as the main unresolved gap.

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 nothing to disambiguate and the description cannot be faulted for parameter coverage. Baseline 4 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?

States a verb (read) and a resource (voluntary infrastructure support options), but 'support options' is abstract and the description does nothing to distinguish it from siblings like resource_offer or independent_extension_guidance, which plausibly overlap. An agent can guess the domain but not the boundary.

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?

No indication of when to call this versus resource_offer or the research/guidance siblings. The only guidance-like content is a negative constraint ('no financial payments'), which says what the tool is not, not when to use it.

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