system_get_recents

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

With no annotations provided, the description fully bears the behavioral disclosure. It explains that the tool returns recent changes, supports filtering by item types, and uses pagination. It does not cover error scenarios or behavior with invalid timestamps, but provides adequate transparency for safe use.

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 well-structured with sections for required fields, optional fields, supported types, workflow tips, and common use cases. It is longer than necessary but front-loads the purpose and uses bullet points effectively. Every section earns its place.

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 covers parameters thoroughly, includes examples, and addresses pagination and filtering. However, it does not describe the response format or return fields, which would be helpful given no output schema. Still, it is largely complete for a retrieval tool.

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?

Input schema coverage is 100%, so baseline is 3. The description adds value by explaining timestamp formats, providing examples for each parameter, and clarifying pagination defaults. This goes beyond what the schema provides.

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 it retrieves recently viewed or modified items after a given timestamp, distinguishing it from sibling list tools like `activities_list` or `deals_list` which are entity-specific. The verb 'Get' and resource 'recent changes' are specific.

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 description explains common use cases (tracking activity, syncing data) and provides workflow tips like using pagination and filtering. However, it does not explicitly state when not to use this tool or compare it to alternatives like `search_universal`.

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