weeklyAnalytics

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

With no annotations, the description must carry the behavioral burden. It indicates a read-only fetch, but does not explain timezone handling, whether the window is rolling or calendar-based, whether the current day is included, or how empty results are represented. This is minimal behavioral disclosure.

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 one compact sentence that immediately states the action, output content, and time scope. Every word is useful and the structure is front-loaded with the core purpose.

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 description names the return content (transaction count and volume breakdown) and the time period, which is sufficient for a zero-parameter tool with no output schema. It could add timezone or exact window semantics, but the core interaction is understandable and callable.

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, so there is no parameter semantics burden on the description. The 100% schema coverage is vacuous but complete, and no parameter documentation is needed.

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 verb 'Fetch', the resource 'transaction count and volume breakdown', and the scope 'last 7 days'. This differentiates weeklyAnalytics from siblings like dailySummary and monthlyAnalytics by its explicit time window.

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 time window 'last 7 days' gives clear context for when this tool should be used, distinguishing it from daily or monthly analytics. It does not explicitly name alternatives or when not to use it, but the usage context is clear and unambiguous.

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