get_event_displayed_host_messages

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the scoping detail 'displayed' and states the return type, but doesn't disclose additional behavioral traits like pagination, auth requirements, or edge-case handling. This is comparable to the calibration example where scoping was noted but scored 3 due to missing richer context.

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 two sentences, front-loaded with the verb and resource, and every sentence adds value. There is no fluff or repetition of schema/annotation details.

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?

This is a simple read-only retrieval tool. Annotations cover safety, schema covers both parameters, output schema presumably covers return shape, and the description clarifies the exact semantic (displayed host messages). Nothing critical is missing for a tool of this complexity.

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%, with both event_id and fields already clearly documented. The description's 'by ID' reinforces event_id but doesn't add substantive meaning beyond the schema. Per calibration, a high-coverage schema means a baseline of 3 is appropriate.

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 uses the specific verb 'Get' with the resource 'host messages displayed on a Partiful event's page', clearly identifying what the tool does. It distinguishes this from sibling tools like get_event_comments or get_event_info by focusing on host messages specifically.

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 provides clear context: you use this tool when you need the host messages displayed on an event page. It doesn't explicitly name alternatives or exclusions, but the wording makes the usage scenario obvious and distinct from related getters.

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