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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds one genuinely new fact — that calling this incurs no charge — but says nothing about quote validity, currency/credit units, or whether repeated quoting is free or rate-limited.

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 no filler; the cost-safety point is delivered first. It is arguably over-lean for a tool whose role in the workflow matters, but every word earns its place.

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?

With no parameters and no output schema, the description must carry the burden of explaining what a quote returns (cost amount, breakdown, expiry) and how it feeds the subsequent scan call — neither is addressed. Annotations cover the safety profile, so this is a moderate rather than severe gap.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. 'One scan' is consistent with the single-unit scope implied by the name.

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 ('Quote one scan'), and the qualifier 'before anything is charged' identifies it as the pre-purchase cost estimate for a conversation scan rather than the scan itself. It doesn't name siblings like soclo_conversations_scan or soclo_conversations_prices, so the boundary is inferred rather than stated.

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?

'Before anything is charged' implies the correct sequencing — call this prior to any operation that would incur cost — which is meaningful implied usage. However, it never explicitly says which follow-up tool consumes the quote (soclo_conversations_scan) or what to do if a quote is stale or rejected.

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