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

The description adds a useful behavioral detail beyond annotations: raw need text is classified in memory and is not stored. This addresses data-handling expectations. However, it does not explain side effects, matching behavior, or response characteristics, so it does not fully leverage the opportunity to clarify behavior.

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 two short sentences with the primary call pattern front-loaded and a useful privacy/storage note appended. It contains no filler, though the phrasing could be slightly more structured for scannability.

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?

For a simple two-parameter tool this is minimally adequate: it names the input need, the output offers, and the non-storage behavior. However, with no output schema, the description does not explain what the offers look like, and it leaves intentKey and sibling-tool differentiation unaddressed.

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%, so the description must compensate, but it only loosely paraphrases the 'need' concept and says nothing about 'intentKey' or how the parameters relate. This leaves an agent without enough information to confidently construct a valid call.

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 concrete action and resource: provide a need and receive current agent-only offers. It is not a tautology and gives enough specificity about the tool's purpose, though it does not explicitly contrast itself with sibling tools like get_agent_market_state.

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?

'Tell NAIF what an agent needs and receive current agent-only offers' implies the tool should be used when an agent needs to obtain offers, but it provides no explicit when-not-to-use guidance or comparison with sibling tools. The usage context is implied rather than clearly routed.

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