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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It provides none: no indication of what the call returns, whether it is read-only, how pricing works, or any side effects. The only behavior mentioned is the cost, which is unrelated to the tool's operation.

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 short, but it is under-specified rather than appropriately concise. It contains no functional information and fails to earn its place as a tool description.

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?

Despite having an output schema and a single required parameter, the complete absence of a functional description means the tool is effectively unusable for correct selection or invocation. The pricing note does not explain what history is returned, what gnaf_id refers to, or how this differs from numerous related siblings.

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 0%, and the description adds no meaning to the single gnaf_id parameter. An agent cannot tell what form the identifier should take or how it is used. The description does nothing to compensate for the schema's lack of documentation.

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 is only 'Price: 80¢ per call.' It does not state a verb, resource, or function. The tool name suggests it returns property history, but the description itself provides no purpose or distinction from siblings like properties_sale_history or properties_rent_history.

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?

There is no guidance on when to use this tool versus any of the many historical tools in the sibling list. The description offers no context, exclusions, or alternatives, leaving the agent to guess entirely from the tool name.

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