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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description does add one genuinely useful behavioral fact — that nothing is charged at quote time — but omits whether the quote reserves capacity, how long it remains valid, or what a caller gets back (no output schema exists to answer that).

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?

Nine words in one front-loaded sentence with no filler. It is efficient, though the terseness comes at the cost of the missing routing and return-value context instead of being paired with it.

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-param cost-estimation step embedded in a lead-finding workflow, the description leaves the workflow unexplained: no indication of which follow-up tool consumes the quote, whether quotes expire, or what happens if you skip this step. With no output schema, the agent has no other source for those answers.

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, which is the baseline-4 case; there is no parameter semantics to clarify. Some value could have been added by explaining how a quote is bound to a search with no inputs, but the schema already tells the agent everything it needs to invoke the call.

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 verb 'quote' plus 'a business search' gives a rough sense that this returns a cost estimate for a search, and the title reinforces it. But it never names the actual resource being quoted (the leads find/search operation, presumably soclo_leads_find) and doesn't differentiate itself from the many other *_quote siblings (soclo_quote, soclo_leads_draft_quote, soclo_creators_search_quote). An agent has to infer the purpose from the name prefix.

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 this is a preflight step, but the description never says 'call this before soclo_leads_find' or states when a quote is required vs optional. No exclusions, no prerequisites, and no mention of any sibling tool despite dozens of adjacent quote tools.

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