Get Oracle open-data property

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does reveal that the tool fetches from IPFS, returns a consolidated JSON, and requires exactly one of three identifiers. But it does not disclose failure modes, not-found behavior, or what happens if the county parameter is omitted or combined with an identifier.

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 compact and front-loaded: the primary action and resource appear first, followed by the key invocation rule. Every sentence earns its place with no redundant or filler content.

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 read-only fetch tool with no output schema, the description names the returned artifact and its composition, and the input schema covers parameter details. The main gap is the lack of explicit error/not-found behavior and clarification of how county interacts with the three identifier options.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by stating the mutual-exclusivity rule ('exactly one of parcelIdentifier, propertyId, or cid'), which the schema does not express through required fields or oneOf constraints. It also implies county is optional context.

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 uses a specific verb ('Fetch') and names a concrete resource ('full consolidated property JSON') with its contents (appraisal, permits, Sunbiz, BBB). This clearly distinguishes it from permit-only siblings like getPropertyPermits, though it does not explicitly name sibling 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 gives an explicit invocation constraint ('Provide exactly one of parcelIdentifier, propertyId, or cid'), which is valuable usage guidance. However, it does not explicitly state when to use this tool versus sibling tools like queryProperties or listOracleProperties, leaving the when-to-use distinction mostly implied by the word 'consolidated'.

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