hs4.resolve.events

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

No annotations provided, so description must disclose behavioral traits. Only states it resolves IDs from natural language; does not mention read-only nature, potential side effects, authorization needs, or that results are likely/probabilistic. Minimal transparency.

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 is concise but underspecified. Could add a second sentence to clarify parameters or output without becoming verbose. It's minimal but lacks completeness.

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 4 parameters (1 required), no output schema, and no annotations, the description is severely incomplete. It omits parameter roles, return value, and how this tool fits into the workflow (e.g., output IDs usable by hs4.events.get). Fails to cover essential context.

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 only references the 'query' parameter implicitly via 'natural-language query'. No explanation of 'limit', 'groupHint', or 'includeEvidence'. Fails to add meaning beyond bare schema.

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 specifies verb 'Resolve', resource 'event IDs', and input 'natural-language query'. It distinguishes from siblings like hs4.events.list or hs4.events.get by indicating fuzzy resolution rather than direct listing or retrieval. Could be clearer about output format (IDs only?).

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 vs alternatives. Does not mention exclusions or prerequisites. For example, when to prefer this over hs4.events.list or hs4.events.get is left implicit.

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