Builder app activity (trades routed through an app)

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

Annotations already establish readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context beyond those annotations: the default time window, why it is narrow (high fill volume), and accepted since/until formats. It does not discuss pagination behavior, but the limit parameter is documented in the schema.

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 sentences, front-loaded with what the tool returns and scoped by builder address, followed by practical time-window guidance. No filler or repetition.

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?

With no output schema, the description still names the returned metrics (volume, builder fees, unique traders, top coins). It covers the key required parameter and the time-format semantics, making it complete enough for an agent to invoke 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 coverage is 75%, with builder and limit well documented. The description adds meaning for since/until by listing accepted Relative, date, date-time, 'now', and Unix ms formats, plus the default 1h window. It does not add much for limit, but the schema already covers that parameter.

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?

States a specific verb and resource: retrieves fills routed through a builder by builder address, with named metrics (volume, builder fees, unique traders, top coins). It implicitly distinguishes itself from the many wallet-oriented siblings by operating on a builder/app address rather than a user wallet.

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?

Gives clear operational context: default window is last 1h because busy builders produce thousands of fills, and it explains accepted time formats. It does not explicitly name when to prefer a sibling, but the builder-address scope makes the intended use clear.

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