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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so 'Read only.' is redundant. The one piece of added context is the word 'current', hinting the price is live and may change between calls, but nothing is said about currency, units, or whether the price is stable.

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?

Two short sentences, front-loaded with the purpose. The second sentence ('Read only.') duplicates the annotations and earns little for its space, but it is not costly.

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, read-only price lookup with no output schema, the description is minimally adequate but omits what the return looks like (amount, currency) and how it relates to the quoting sibling. An agent knows what to call but not quite when or what to expect.

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?

Zero parameters and 100% coverage on an empty object schema; there is nothing to disambiguate, so the baseline of 4 applies.

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: 'Show the current price of one scan.' An agent can immediately tell this is a pricing lookup for the conversation scan feature. It does not, however, distinguish itself from the close sibling soclo_conversations_scan_quote, which sounds similar.

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?

No guidance on when to use this versus soclo_conversations_scan_quote or soclo_conversations_prices/scan_status. The only usage signal is 'one scan', leaving the agent to infer the distinction from sibling names alone.

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