hs4.events.list

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

No annotations are provided, so the description carries full burden. It only states 'list' which implies read-only, but does not disclose behavior such as pagination, maximum limit, or whether filters are case-sensitive. No mention of side effects or performance.

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?

Single sentence with no wasted words. Concise and direct, but could benefit from structuring parameter details separately.

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?

Given no output schema, incomplete parameter descriptions, and lack of behavioral transparency, the description is insufficient for an agent to fully understand the tool's capabilities and usage constraints.

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 0%, so description must compensate. It mentions 'group/name filters' which loosely map to groupContains and nameContains, but does not explain the meaning of limit, nor specify that nameContains filters by partial match. The parameter semantics are incomplete.

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?

Description clearly states verb 'list' and resource 'HS4 events', and mentions optional filters. This distinguishes it from sibling tools like hs4.events.get (likely single event) and hs4.events.run, though it doesn't specify the scope of events listed.

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?

No guidance on when to use this tool versus alternatives like hs4.events.get or hs4.events.run. Lacks context for preferred usage scenarios.

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