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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does disclose payment requirements (FABER x402, $0.02, Base Mainnet, USDC), which is useful beyond the schema, but it does not describe the output format, failure modes, or limitations beyond 'concept-level'.

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 two sentences with no filler. The purpose is front-loaded, and the payment details are relevant and concise, making every sentence earn 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?

Given the nested request object, no output schema, and sparse parameter descriptions, the description should explain the inputs and expected output. It only covers a high-level purpose and payment, leaving the agent to guess what `location` and `goal` should contain and what the concept-level output looks like.

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 description coverage is only 50%, yet the description does not add meaning to the required request parameters. It mentions 'site conditions' but never connects that to the request object's `location` and `goal` fields, leaving the agent without guidance on how to populate them.

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 produces concept-level solar, thermal, cooling, cleaning, and storage considerations from site conditions. It identifies a specific verb, resource, and source, and the unique combination of these domains distinguishes it from sibling tools, though it does not name alternatives.

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 implies a use case—generating concept-level considerations from site conditions—but gives no explicit guidance on when to use this tool versus the sibling faber_* tools. There are no exclusions or alternatives mentioned, leaving the decision to agent inference.

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