B3TR: App overview (totals)

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

Annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description adds details about the data returned (rewards, actions, sustainability, rankings) and the filtering constraints (mutually exclusive date/roundId). No contradictions 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 sentences efficiently convey purpose, endpoint, return values, and critical usage notes (bolded warning). No unnecessary words; front-loaded with key information.

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?

Given the presence of an output schema (context shows 'Has output schema: true'), the description sufficiently covers what the tool returns. Annotations cover safety. Sibling list shows this is one of many B3TR tools, and the description distinguishes it well.

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%, but the description adds significant context beyond schema, especially for appId: clarifying it must be a 32-byte hex veBetterDaoId and instructing to use getAppHubApps for name resolution. This is not present in the schema description.

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 it gets an APP overview for a specific app listed on veBetterDao, specifying the endpoint and listing returned data (totals, rewards, rankings). It distinguishes from siblings like getB3TRAppsLeaderboard, which returns a leaderboard, and getB3TRActionsForApp, which returns actions.

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 states when to use: for a specific app overview. Provides critical guidance on appId format (veBetterDaoId, not app name) and advises to call getAppHubApps first if user provides a name. Also notes mutual exclusivity of date and roundId filters.

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