solvscore_decision_info

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses pricing (0.001 USDC via x402 on Base), the required X-Payment header, response contents, and that malformed bodies return HTTP 422 before the payment gate — but all of that describes an HTTP request the tool cannot issue, since the schema accepts no arguments and forbids additional properties. That framing actively misdirects the agent about what invoking this tool will do.

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 text is a single dense run-on block that embeds a URL, a JSON literal, and header names rather than front-loading the tool's purpose. It is also cut off mid-sentence ('only real'), leaving the final clause dangling and unusable.

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 informational tool with no output schema, the description should state what the caller receives. Instead it documents an external endpoint's contract, and the truncation removes whatever point the sentence was building toward, so an agent cannot confidently predict this tool's output or side effects.

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 the baseline would normally be a 4. However, the description introduces two apparent parameters ('agent' and 'principal_usd') in a JSON body that do not exist anywhere in the input schema, creating a false expectation about what must be supplied. This is not additional meaning beyond the schema but contradicting it.

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 opening clause does state a specific resource ('Info about the SolvScore Single Decision API'), but the remaining text describes an HTTP POST call rather than what this zero-parameter tool returns, so an agent cannot tell whether invoking it performs a purchase or merely returns documentation. No attempt is made to distinguish it from close siblings such as solvscore_repgate or solvscore_vjps.

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 '[FREE]' tag hints that this is a no-cost way to learn about the paid decision endpoint, but there is no explicit when-to-use/when-not guidance and no named alternative for actually obtaining a decision. The agent is left to infer the relationship between this info tool and the payment-gated endpoint on its own.

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