get_last_events

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

The description reveals that Semaphore returns the last 200 events and that the limit parameter trims on the MCP side. Since no annotations are provided, this information is valuable for understanding inherent constraints and behavior.

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 concise and well-structured: a single-line purpose, a sentence on underlying constraints, then parameter and return value documentation. Each sentence serves a clear function with no repetition.

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 list tool with one parameter, the description covers purpose, behavior (200-event limit), parameter semantics, and return type. No gaps or missing information is apparent.

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 description explains the limit parameter: it returns the most recent N events, with 0 meaning all returned events. This adds crucial context beyond the schema's type and default, compensating for 0% schema coverage.

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 lists 'last global events visible to the current user', specifying the verb, resource, and scope. This differentiates it from siblings like 'list_events' and 'list_project_events'.

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 implies use for recent global events but does not explicitly state when to use this tool over alternatives like 'list_events' or 'list_project_events'. No exclusions or context is provided.

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