get_activity

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds genuine behavioral context beyond those annotations, including pagination limits (page, size), the maximum page size of 50, and the cap of 500 latest entries.

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 compact and front-loaded: the first sentence states the tool's purpose, and the second provides the only additional operational detail needed for pagination. Every sentence earns its place with no filler.

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 read-only list tool with two optional, fully documented parameters, the description is nearly complete. Minor gaps remain, such as the exact ordering of results and what 'recent' means, but an agent can invoke this tool correctly with the given information.

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 description coverage is 100%, so the schema already fully documents both parameters. The description reinforces the defaults and maximums but doesn't add substantial new meaning beyond the schema, matching the baseline expectation for fully covered parameters.

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 identifies the operation ('list recent activity') and the resource (SimpleLocalize project), and gives concrete examples of activity types. However, it doesn't explicitly distinguish itself from the sibling tool get_activity_changes, which could overlap with the 'changes' category.

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 says what the tool does but gives no guidance on when to use it over alternatives. The sibling tool get_activity_changes suggests a possible different purpose, but the description doesn't clarify whether to use get_activity or get_activity_changes for a specific need.

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