splithub_analytics_events

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

With no annotations, the description still discloses meaningful behavior: the data source differs by deployment (cloud raw tail vs self-hosted user database) and retention is 7 days free / 30 Pro, which directly limits what results can exist. It omits read-only confirmation, ordering, and whether the result is capped by the limit.

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?

Two tight sentences, action and scope front-loaded, with the deployment caveat parenthesized where it belongs. The 'raw tail' phrasing is slightly cryptic but nothing is wasted.

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?

No output schema and no annotations, so the description should say more about the return shape (event list vs counts, fields, ordering) and the property identifier format. It covers the deployment/retention model well but leaves the agent guessing on what it will actually receive.

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 coverage is 0%, so the description must carry parameter meaning. It identifies 'property' only as an analytics property (no format: ID, slug, or name) and never addresses 'limit' at all, despite the schema capping it at 200. 'Latest' hints at a tail but does not explain the parameter.

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?

Names a specific resource and scope: 'the latest raw pageviews and custom events of an analytics property', with 'raw' contrasting against the aggregate siblings (splithub_analytics, _funnel, _paths, _retention). It does not explicitly name those siblings, but an agent can tell this is the event-level tail rather than an aggregated report.

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?

Gives one concrete scenario: 'Use to check that tracking works after wiring track() or sh.js.' That is clear positive guidance, but there is no indication of when to prefer splithub_analytics_realtime or splithub_experiment_events instead, and no exclusions.

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