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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one behavioral fact – results are limited to 'recent' activity – but does not say how recent, whether results are ordered or capped, or whether they are scoped to the authenticated account.

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?

It is a single short fragment with zero waste, which is good, but it reads as under-specification rather than deliberate economy. A verb-led sentence would have cost no more space and carried far more 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?

With no input parameters and no output schema, the description is the only place an agent can learn the return shape, and it only names three entity types without stating count limits, ordering, or the recency window. Adequate as a hint, insufficient as a specification.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The entity types mentioned are return content, not inputs, so no credit or penalty beyond the baseline.

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 enumerates what 'activity' consists of (payments, deposits, connections), which adds meaning beyond the tool name. But it is a bare noun phrase with no verb and no scope definition – 'recent' is undefined, and it does not distinguish itself from siblings like get_banking or list_recipients.

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?

There is no statement of when to use this tool rather than get_banking, get_wallet, or list_recipients. The agent must infer from the returned entity types that this is the transaction-history view, which is a stretch given the terse phrasing.

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