Location & Demand Intelligence

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

Annotations already indicate the tool is not read-only, not idempotent, and not destructive. The description adds that it is an unofficial, independent actor not affiliated with the source publisher, and mentions a per-call cost. This provides some context beyond annotations, but does not disclose specifics about what actions are dispatched or how the routing behaves. No contradiction with annotations.

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 two sentences: the first front-loads the core purpose, and the second provides a disclaimer and pricing. Every sentence adds value, with no wasted words.

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?

While the input schema is rich with parameter descriptions and contextual notes (e.g., mapping AFAD events to assets), the top-level description lacks an explanation of the output format or the nature of the 'actions' produced. There is no output schema, so a bit more context would help. However, the schema's own description mitigates some gaps, so this is minimally adequate.

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 100%, so the input schema fully documents all 11 parameters and their semantics. The description adds no additional parameter information, which is acceptable when schema coverage is complete. Baseline score of 3 applies.

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 'Turn official AFAD events into distance-based asset and route actions' clearly identifies the verb (turn), resource (official AFAD events), and output (distance-based asset and route actions). This distinguishes it from sibling scorer tools, which focus on scoring destinations and demand rather than operational routing.

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 implies usage for processing AFAD earthquake event data into asset/route actions, but does not explicitly state when to prefer this tool over alternatives or provide exclusion criteria. There is no mention of alternative tools or conditions under which this tool should not be used.

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

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

Annotations include readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds useful context beyond annotations: it discloses the per-call cost ('$0.02/call, x402 (USDC on base)') and the tool's unofficial, non-endorsed status. However, it does not clarify what side effects (if any) occur despite readOnlyHint=false, nor does it explain external dataset behavior beyond the openWorldHint. The description does not contradict the annotations, so no flag, but it leaves room for more transparency.

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 two sentences: the first states the purpose, the second provides critical context (independence and pricing). It is front-loaded, free of fluff, and every sentence contributes meaning. This is a model of conciseness.

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?

The tool has 7 required parameters and no output schema. The input schema explains all parameters in detail, but the description does not specify what the tool returns (e.g., a score, a ranked list, or a pricing breakdown). Given the complexity and lack of output schema, the description is somewhat incomplete. However, the schema's rich parameter descriptions partially compensate, and the core purpose is clear.

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 100%, and each parameter has detailed meaning (e.g., railWeight 'Share of the final score assigned to metro proximity', maxTotalChargeUsd 'Maximum accepted total run charge'). The tool description itself adds no parameter-level detail, but the schema bears the full burden. Since coverage is high, the baseline score of 3 applies; the description does not need to compensate.

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 the specific verb 'Score' and clearly identifies the resource: 'customer sites against official Metro stations and İSPARK capacity.' This distinguishes it from sibling tools focused on other location-based scoring (e.g., neighborhood-age-demand, solo-household-demand), showing a unique transit/parking access focus. The schema description reinforces this by mentioning 'Ranks customer-supplied Istanbul sites using straight-line proximity...'

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 offers no guidance on when to use this tool versus alternatives. It does not mention sibling tools, exclusions, or preferred use cases. The only contextual hint is the mention of being 'Unofficial, independent Actor,' which is about trust, not usage. There is no explicit 'use this when...' or 'for other scoring needs, see...' guidance.

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

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

The description adds useful context beyond annotations, including that it is unofficial, independent, and costs $0.02/call. However, despite readOnlyHint=false and openWorldHint=true, it does not disclose any side effects, external data access, or operational behavior.

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 extremely concise: two sentences deliver the core purpose and important independence/pricing disclaimers. Every word earns its place with no redundancy.

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?

The tool has no output schema, so the description should explain what the result of 'scoring' looks like; it does not. It also doesn't mention open-world behavior or data source handling. The description covers purpose and price but remains incomplete for a scoring service.

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 input schema provides full coverage (100%) for all five parameters, so the description is not required to repeat them. The only semantic addition is 'customer-defined weights' which maps to cohortWeights, but no further parameter-specific meaning is added.

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 the tool's function: scoring neighborhoods using official resident age cohorts and customer-defined weights. It distinguishes itself from the sibling MOIS solo-household scorer via the 'age' focus, though it doesn't explicitly name that sibling.

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 offers no guidance on when to use this tool over the sibling scorers or other alternatives. There are no contextual cues, exclusions, or example scenarios.

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

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

Annotations already provide safety hints (readOnlyHint: false, destructiveHint: false). The description adds valuable behavioral context beyond annotations: it discloses that the tool is an 'Unofficial, independent Actor' and states the cost ('$0.05/call, x402 (USDC on base)'), which is useful for the agent. It does not detail rate limits or response behavior, but the added cost/affiliation transparency earns a solid 4.

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: one sentence for core purpose, one sentence for disclaimers and pricing. Every clause adds information, with no filler or repetition. The most important action ('Rank') appears first, so it is well-structured and front-loaded.

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 scoring tool with 5 fully documented parameters and no output schema, the description explains the essential purpose and provides pricing/affiliation context. It does not fully explain what the ranking output looks like or how it differentiates from the sibling scorer, but the schema and annotations cover most of the necessary context. A 3 would undervalue the explicit cost and independence disclosure, so 4 is fitting.

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 input schema has 100% description coverage, including clear explanations for each parameter (e.g., ageWeights with non-overlapping bands, targetLegalCodes with 10-digit codes). The description does not add extra parameter-level meaning beyond mentioning 'age composition', so the baseline of 3 is appropriate.

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 states a specific action ('Rank territories') with a specific resource ('official one-person-household age composition'), making the purpose clear. However, it does not explicitly distinguish from the very similar sibling tool 'mois-neighborhood-age-demand-scorer', so it stops short of a 5.

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 implies use when ranking territories by solo-household age composition, but gives no explicit guidance on when to choose this tool over its sibling 'mois-neighborhood-age-demand-scorer' or any other alternative. There is no mention of exclusions or preferred context.

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

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

Annotations already indicate read-only and non-destructive behavior. The description adds the 'Free' cost and explicitly enumerates returned fields (price, payTo, network), providing useful output context beyond the annotations.

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?

Two concise sentences: the first states what the tool does and its output fields, the second gives the usage instruction. No redundancy or unnecessary detail.

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 no output schema, the description fully covers invocation context, result contents, and when to call it. It is self-sufficient and leaves no critical gaps.

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 schema description coverage is 100%, so the baseline of 4 applies. The description focuses on purpose and output, which is appropriate given no parameters need explanation.

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 it lists every paid tool in the 'location-demand-intelligence' bundle with price, payTo address, and network. The verb 'list' and specific resource distinguish it from sibling scoring tools.

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?

Explicitly instructs to call this first if no wallet is ready, giving a clear condition and priority. This effectively communicates when the tool should be used as a prerequisite for paid tool interactions.

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

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

The description adds valuable non-obvious context beyond annotations: it discloses that the tool is 'Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher' and provides pricing ('$0.02/call, x402 (USDC on base)'). These details supplement the openWorldHint and readOnlyHint flags with cost and affiliation information. It does not contradict annotations, and no major behavioral gaps remain glaring.

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 two concise sentences: the first states the core function, and the second adds necessary caveat and pricing info. Every clause earns its place, and the structure is front-loaded with the purpose. No redundant or verbose language.

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?

The tool has 7 parameters and no output schema. While the input schema is rich, the description does not explain what the tool returns (e.g., benchmark results, comparative metrics, or reports). The name 'benchmark' hints at the output, but the agent is left without clear expectations about the response structure, especially given the tool's cost and independence caveat. A statement about return format would complete the context.

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?

With schema description coverage at 100%, all parameters already have detailed descriptions in the input schema. The main description adds no parameter-specific meaning beyond what the schema provides. The schema itself explains idempotency, limits, and field semantics thoroughly, so the baseline score of 3 is appropriate.

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 the tool's function: 'Compare customer-owned property facts with licensed public Sahibindex market reports.' It specifies the verb (compare), the resource (property facts vs. market reports), and the scope is evident from the name and sibling context (benchmark for property markets). This distinguishes it from the unrelated sibling tools.

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 implies usage (comparing property facts against market reports) but does not explicitly state when to use it vs. alternatives. The input schema adds a negative constraint ('Listing URLs and listing-page scraping are not supported') but no positive use cases or alternative tool exclusions. Since the purpose itself provides enough context to infer when to invoke, it earns a 3; however, it lacks explicit guidance.

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

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

The description discloses pricing ('$0.02/call'), payment method ('USDC on base'), and independence ('Unofficial, independent Actor'), which go beyond the annotations. It does not contradict annotations and adds context not available from structured fields.

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 extremely concise (two sentences) with the core purpose front-loaded, followed by essential disclaimers and pricing. Every sentence earns its place with no redundancy.

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?

The tool has moderate complexity and no output schema, yet the description does not explain the return format or how the operating windows are computed beyond stating the conversion. It remains adequate for selection but not fully sufficient for invocation without relying on the schema's input descriptions.

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% with detailed parameter descriptions, so the baseline is 3. The main description adds no extra parameter semantics beyond the high-level 'traffic history into windows' concept, but schema already handles the burden.

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 states a specific verb ('Convert') and resource ('official hourly traffic history') with a clear output ('explainable low-congestion operating windows'). This clearly distinguishes it from sibling tools focused on earthquakes, parking, and real estate.

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 explicit when-to-use or when-not-to-use guidance is provided. The description only states what the tool does, leaving usage to be inferred from the domain and tool name.

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