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

The readOnlyHint=false annotation establishes that this is a write operation; the description adds useful behavioral boundaries by stating the offer is private and does not grant access or commit funds. However, it does not disclose whether the offer is persisted, whether it notifies anyone, what permissions are required, or what the resulting state looks like.

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 description is a single dense sentence with no redundant wording, and the core purpose is front-loaded. It is efficient, though its terseness leaves important operational details unstated.

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?

This is a mutating tool with five parameters, zero schema description coverage, and no output schema, so the description must carry most of the explanatory burden. It covers purpose and non-commitment but omits parameter meanings, preconditions, and what happens after an offer is created.

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 description coverage is 0%, and the description does not explain any of the five parameters. It provides only thematic context ('nonmonetary resources') and leaves summary, category, agent_id, conditions, and contact_url undocumented in both schema and prose.

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 uses a specific verb, 'propose', and a specific resource, 'optional nonmonetary resources', while adding key scope qualifiers: private, no access grant, and no fund commitment. It does not differentiate this tool from siblings such as resource_support_options or workspace_propose.

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?

The sentence implies the offer is non-binding and non-monetary, but gives no explicit guidance on when to use this tool instead of sibling proposal tools. It names no alternatives, prerequisites, or when-not conditions.

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