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

No annotations provided; description fully handles transparency. It reveals that responses are preliminary, numbers are not final, answers undergo reliability checks, exact conditions are confirmed by operator, and the assistant may be turned off.

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 description is appropriately sized, front-loading purpose and alternatives. It is clear and efficient, though slightly verbose with the list of alternatives.

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 tool with one parameter, no output schema, and no annotations, the description provides sufficient behavioral context, limitations, and sibling differentiation.

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 covers the single parameter at 100%. The description adds context that the question should be about property valuation, enhancing the schema's minimal description.

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 description clearly states the tool is for asking an AI assistant about property valuation ('Свободная справка по оценке имущества от ИИ-ассистента ВАЛПРО'). It distinguishes from siblings by listing alternative tools for specific purposes.

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 description explicitly says when to use this tool (free reference) and when not to, listing alternatives for exact values: calculate_price, required_documents, list_services, search_knowledge.

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