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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering key safety traits. The description adds that the snapshot is 'short-lived' and requires an owned bag, providing useful context. However, it does not disclose the return value or any operational constraints beyond ownership.

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, front-loaded sentence that conveys the core action without filler. Every word contributes to understanding the tool's purpose.

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?

The tool is simple (2 params) and annotations cover safety, but the description omits usage guidelines, return information, and explicit parameter semantics. It is minimally viable but leaves gaps for an AI agent to infer, especially around what the session is for and what happens when invoked.

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?

With 0% schema description coverage, the description must compensate for missing parameter meanings. It only implicitly maps 'owned bag' to bagId and 'provider' to providerPubkeys, but it does not explain the exact purpose, format, or relationship between the two parameters. This is insufficient given the absence of schema descriptions.

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 the specific verb 'Freeze' and identifies a clear resource: 'a short-lived live provider and shared-balance snapshot for an owned bag.' This distinguishes it from sibling tools like provider_funding_preview and provider_quote, which likely serve different purposes. The title 'Create provider funding session' aligns with the description.

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 phrase 'for an owned bag' implies a prerequisite, but the description gives no explicit when-to-use, when-not-to-use, or alternative guidance. Usage is only inferred from the verb and resource, without contrasting with sibling storage tools.

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