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 explaining behavior, but it only mentions price. It fails to disclose whether this is a read operation, what data it returns, any side effects, or any context such as required permissions or output structure.

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 this is under-specification rather than effective conciseness. The single price sentence provides no functional information and does not earn its place in a tool definition meant to guide tool selection and invocation.

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?

Even with an output schema present, the description is missing the most essential information: what the tool does and when to use it. Given the large number of similar property tools, this definition is wholly inadequate for an agent to invoke it correctly.

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%, so the description must explain what 'gnaf_id' means or how it should be formatted, but it says nothing about the parameter. The agent is left with only the raw schema and a field name with no semantic guidance.

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 contains only 'Price: 23¢ per call.' and does not state what the tool does. The name hints at returning all basic property information, but no verb, resource, or scope is defined, and nothing distinguishes it from sibling tools like properties_basics_bed_count or properties_basics_dwelling_type.

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 alternatives. With dozens of property-related siblings, the absence of any selection criteria leaves the agent unable to choose this tool correctly.

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