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

With no annotations, the description carries the disclosure burden and does well: it explains the privacy model (fresh zero-knowledge key, gateway cannot identify the asker) and the cost behavior (spends the model's price in questions). It omits error behavior, rate limits, and return details, but adds substantial behavioral context beyond the schema.

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?

Three short sentences, front-loaded with the action and followed by the two decision-relevant traits: privacy and cost. Every sentence adds useful information without waste.

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?

Covers the key considerations for this paid private query tool: privacy guarantees, question spending, and where to find model IDs. Since there is no output schema, it could explicitly state that the model's answer is returned or describe insufficient-balance behavior, but overall it is complete enough for correct invocation.

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%, so the baseline is 3. The description reinforces that model IDs come from the models tool, but it does not add syntax or meaning beyond what the schema already provides for question, model, or system.

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 specific verb and resource: 'Ask one of PARANOID's AI models a question,' with the additional qualifier 'in private.' This clearly distinguishes it from sibling tools like models, balance, and buy, which are listing/pricing/purchasing operations.

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 primary use case is clear: ask a model a question privately. It also points to the models tool for model IDs/pricing, giving useful context. However, it does not explicitly name the buy or balance alternatives or state when not to use this tool, so it falls short of a 5.

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

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

With no annotations, the description carries the full behavioral burden. It discloses that the result is membership-scoped and time-limited, but does not explicitly state that the operation is read-only, requires authentication, consumes no questions, or describes the response format.

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, efficient sentence that front-loads the key returned information. There is no wasted wording.

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 zero-parameter query with no output schema and no annotations, the description sufficiently explains the return values: remaining questions and expiration date. Minor gap is lack of explicit authentication or current-membership context.

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 has zero parameters, so there is no parameter semantics to explain. Baseline score of 4 is appropriate for a no-parameter tool.

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?

Clearly states the resource and returned information: remaining question count and last usable day for this membership. It is specific enough to distinguish from siblings like ask, buy, and models, though it lacks an explicit verb such as 'returns'.

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?

Usage is implied: check remaining question quota and expiration, likely before calling ask or buy. However, it does not explicitly say when to use this tool versus alternatives or mention prerequisites.

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

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

With no annotations, the description carries the full load and does well: it discloses the paying wallet (PARANOID_PAYER), exact pricing (0.002 USDC per question + 0.30 setup), the 250-question floor, and the side effect that an existing membership is retained beside the new one. It omits failure/irreversibility behavior for a real-money payment and never says what a successful call returns.

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?

One dense sentence covering purpose, cost, minimum and side effect, with the action front-loaded. Phrasing is slightly run-on and the wallet/file details interleave, but nothing is padding.

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 one-parameter payment tool with no annotations and no output schema, the description covers cost, chain, wallet, minimum and persistence of prior membership - enough to invoke correctly. Remaining gaps are payment failure handling and return payload, which is what keeps it from a 5.

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 parameter is documented, so the baseline is 3; the description earns an extra point by tying 'questions' to a per-question price and a hard minimum, letting the agent compute total cost (e.g. 250 questions = 0.80 USDC) before calling.

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 specific verb and resource (buy a membership) plus the payment rail (x402 USDC on Solana) and the wallet used, which is unambiguous against siblings ask/models/balance. An agent knows exactly what the tool does without opening the schema.

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?

Implies the usage context clearly - you buy a membership when you need a question quota - and the note that an existing membership is preserved gives the agent a reason it may still be safe to call. It never names an alternative or an explicit when-not condition, which keeps it below a 5.

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

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

No annotations are provided, so the description carries the full burden, but the tool takes zero parameters and is an obvious read-only listing. The one genuinely useful behavioral disclosure is that cost is expressed per single message/question sent to each model. It does not state auth or quota requirements, pagination, or ordering of results.

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 with the verb first and no filler. Every clause carries information: what is listed and what extra attribute accompanies each item.

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 no-parameter, no-output-schema listing tool, the description covers both the collection returned and the key per-item attribute (cost). Only minor gaps remain, such as the shape of the returned list or whether identifiers from it feed into 'ask'.

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 has zero parameters, so there is no parameter semantics to explain; the baseline for a no-param tool applies. Nothing in the description contradicts or muddies the empty schema.

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 specific verb ('List') and resource ('models') and adds the distinctive payload detail: the per-message question cost for each model. This is unmistakably different from the siblings ask/balance/buy, though it never explicitly names or rules out an alternative.

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?

There is no explicit when-to-use or when-not-to-use guidance. The mention of per-message cost implies the tool is a lookup to consult before choosing a model for 'ask', but the agent must infer that workflow rather than being told.

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