get_base_activity

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

No annotations are provided, so the description carries the transparency burden. It does disclose a cost of $0.002 USDC, which is a unique behavioral trait, and outlines the specific data fields returned. However, it does not mention data freshness, latency, rate limits, or whether the data is historical or real-time, leaving some openness about behavioral characteristics.

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 a single, well-structured sentence that front-loads the action and resource, then lists key specifics, and ends with a cost notice. Every word contributes value with no redundancy or filler.

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 simple tool with no parameters and no output schema, the description adequately covers the purpose, the key data points, and the associated cost. It is complete enough for an agent to select and invoke correctly, though a note about the data type (e.g., live vs. delayed) would have made it fully comprehensive.

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 no parameters, so the description does not need to explain parameter meanings. As per the baseline for zero parameters, a score of 4 is appropriate. The description adds clarity about the tool's scope without needing to address parameter semantics.

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 a specific action ('Get') on a specific resource ('Base Mainnet network activity') and lists concrete data points (TPS, block stats, gas utilization). It distinguishes itself from sibling tools like get_gas_prices or get_market_overview by focusing on the Base network specifically.

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 context through its focus on Base Mainnet, but it does not explicitly state when to prefer this tool over alternatives or mention any exclusion conditions. There is no direct comparison to sibling tools or guidance on using it for Base-specific metrics versus other network metrics.

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