get_recent_activity

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

No annotations are present, so the description must carry the behavioral burden. It implies a read-only operation ('See') but does not disclose return format, data scope, pagination, or any side effects. The description is too thin to inform the agent about the tool's behavior beyond a basic intent.

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, focused sentence that directly conveys the tool's purpose without redundancy or extraneous detail. It is optimally concise and well-structured for a simple read tool.

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 one-parameter tool with no output schema, the description gives the essential function and time window. However, it lacks context about what 'activity' includes, the nature of the return value, and differentiation from closely related sibling tools, making it only minimally sufficient.

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 input schema fully documents the 'minutes' parameter with a description and default value, achieving 100% coverage. The description's phrase 'last N minutes' mirrors the schema without adding new semantic meaning, so the baseline of 3 is appropriate.

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 tool retrieves recent user activity over a specified time window ('See what you've been doing in the last N minutes'), using a specific verb and resource. It is concise and understandable, though it does not explicitly distinguish itself from sibling tools like get_timeline or get_app_usage.

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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives, any prerequisites, or scenarios where it would be inappropriate, leaving the agent without direction for selection.

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