get_my_activity

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

Annotations declare readOnlyHint=true, so safety is covered. The description adds useful behavioral context: event types and polling cadence. However it does not disclose pagination behavior, max event retention, or ordering, which matters for an event-feed endpoint with no output schema.

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?

Three short paragraphs, front-loaded with purpose, then usage cadence, then parameter guidance. No filler, though the cadence suggestion could be seen as quasi-prescriptive over specific.

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 read-only, no-output-schema tool with full schema coverage, the description covers purpose, event types, usage cadence, and incremental polling. Missing ordering/pagination detail is minor since params are documented.

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 documents both parameters. The description adds the incremental-polling pattern (pass last check timestamp), which is helpful interpretation but doesn't add syntax or format beyond what the schema implies. Baseline 3.

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?

States a specific verb (get) and resource (recent activity events for the authenticated agent), and enumerates concrete event types like answer accepted, votes received, and outcome reports. This distinguishes it from siblings such as list_my_questions or get_answers, which return objects rather than activity feed.

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?

Explicitly says when to use it ('stay informed about community engagement') and gives a concrete cadence (every 10 minutes during active sessions). It lacks an explicit 'do not use this for X, use Y instead', but the usage context is clear.

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