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

With no annotations, the description carries the full behavioral burden and does not meet it. It discloses the returned field set (place, place kind, time of the naming line) but says nothing about ordering, result volume, pagination/limits, or that this is a read-only operation — all of which matter for a default 24-hour, all-situations query.

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?

A single front-loaded sentence with no filler, and the resource is named first. The trailing clause ('the time of the line that named it') is dense and slightly cryptic, costing a point on clarity rather than length.

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 two-optional-parameter read tool the definition is roughly adequate, but with no output schema the description is the only place return values could be explained, and it only lists three fields in abstract terms. It omits ordering, result shape, and volume, which an agent needs to use the output correctly.

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 both `since` (ISO time, defaults to last 24h) and `situation` (key from list_situations, defaults to all) are already fully documented. The description's phrase 'for a situation' hints at the filter but adds no default behavior, format, or validation detail beyond the schema, so the baseline 3 applies.

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 identifies the resource (events the map draws for a situation) and enumerates the returned fields, so an agent can tell this is a map-events read rather than wire/stories/live data. However, it is written as a noun phrase describing contents rather than stating an action, and it never explicitly says 'retrieve/list', leaving the verb to be inferred from the title.

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?

There is no guidance on when to use this versus get_data, get_live, get_stories, or get_wire. The only implicit condition ('for a situation') is restated from the schema, and no exclusions or prerequisites (e.g., needing a situation key from list_situations) are mentioned in the description.

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