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

With no annotations, the description carries the full transparency burden and does well. It discloses that the call is free, that a missing model causes self-initialization of a scaffold with all registered tools at 0 sats, and that output contains 'No economic data from code.' This surfaces a meaningful side effect and a likely misconception, going well beyond a terse 'Get pricing model'.

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?

Three short sentences with no filler. The core purpose is front-loaded first, followed by two high-value clarifications about cost and initialization behavior. Every sentence 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?

For a zero-parameter tool with an output schema, this description is complete. It covers what is fetched, for whom, the cost, the edge case of no existing model, and the nature of the returned data. Nothing needed to safely invoke the tool is missing.

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 has zero parameters and the schema already documents this fully with 100% coverage. The baseline for 0 params is 4, and the description appropriately focuses on behavior rather than parameter details, since there are no parameters to clarify.

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 a specific verb and resource: 'Get the active pricing model for this operator.' It differentiates from the many sibling tools by naming the exact object returned and adding delimiting facts like 'Free' and 'No economic data from code.' An agent can distinguish this from set_pricing_model, reset_pricing_model, and check_price without guessing.

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 intended use is implied: call this when you need the active pricing model for the current operator. However, it does not explicitly say when to prefer this over alternatives, nor does it mention related siblings like set_pricing_model or reset_pricing_model. It provides context but leaves the comparison to the agent.

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