Size a technology's adoption

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

Annotations already mark the tool as read-only and open-world, so the description only needs to add context beyond that. It usefully discloses the 1-credit cost and clarifies the output content (adoption breadth plus top countries). 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?

Three short sentences with no filler: the core behavior is front-loaded, a practical use case follows, and the credit cost is a useful closing note. Every sentence earns its place.

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 one-parameter read-only lookup with no output schema, the description covers input, expected output, example usage, and cost. It could be slightly more precise about what 'how widely it is used' means (e.g., site count, percentage), but the description is sufficient for an agent to call the tool 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 100%, and the schema already explains that 'technology' is a StackScan-specific name with examples. The tool description adds an example use case but no additional format, normalization, or edge-case guidance, 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 opens with a specific verb and resource: 'Given a technology name, return how widely it is used and its top countries by adoption.' The example 'how many sites run Shopify, and where?' makes the purpose concrete, and the technology focus clearly distinguishes it from sibling tools that target companies or domains.

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 two explicit use cases — 'size a market or compare platforms' — and provides an illustrative query. It does not explicitly state when not to use this tool or contrast it with sibling alternatives, but the usage context is strong enough for most cases.

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