Retrieve a commercial building profile for any US property address including building class, year built, total rentable square footage, floor count, primary tenants, property management, ownership entity, recent renovations, parking ratio, and transit access. Premium API. Cost: $0.25 USDC via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | US property street address |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations set readOnlyHint=false and destructiveHint=true, but description describes a read operation ('Retrieve'). This is a direct contradiction. Description does not disclose other behavioral traits besides cost.
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?
One sentence listing fields and cost; front-loaded with purpose. Efficient but no structural formatting (e.g., bullets) that could improve readability.
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?
No output schema provided, despite returning many fields. Contradiction with annotations and lack of usage guidance make the description incomplete for an AI agent to fully understand behavior.
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 describes the single parameter 'address' as 'US property street address'. Description adds 'any US property address' but no significant extra meaning. Baseline 3 due to 100% schema coverage.
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?
Description clearly states the verb 'Retrieve' and the resource 'commercial building profile' for a US property address, listing many specific fields. However, it does not explicitly differentiate from sibling tools like interzoid_property_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?
No guidance on when to use this tool versus alternatives. Only mentions 'Premium API' and cost, lacking any context for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct data operations (matching, standardization, enrichment) with clear descriptions. Minor overlaps exist, e.g., address_match_advanced vs global_address_match, but descriptions differentiate them.
All tools follow a consistent 'interzoid_descriptive_function' pattern in snake_case, making it easy to predict purpose from the name.
58 tools is high for a single server, exceeding the typical 3-15 range. While each serves a specific data enrichment function, the quantity may overwhelm agents without clear categorization.
The tool surface covers a broad domain including address, company, person, and financial data. Minor gaps exist (e.g., no reverse IP lookup, limited social media coverage), but core data needs are well-addressed.
