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

Beyond the readOnlyHint annotation, the description reveals important access-control behavior, including exactly which fields each role can see and which are never exposed (e.g., sponsors never get email/NDA/check-in state). It also documents required auth scopes, giving the agent a clear picture of expectations and limitations.

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 dense but each sentence earns its place, covering role-based views, return shape, and scopes. It front-loads the core purpose ('The attendee list') and organizes the role details clearly, though it is slightly long.

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 read-only roster tool with no output schema, the description is quite complete: it explains the return shape, role-based redaction, and required scopes. The main gap is underspecified parameter semantics, particularly eid and allowed role values, but overall the agent has enough context to use the tool effectively.

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?

The description mentions the args shape ({ eid?, role? }) and explains role is a filter, but it does not define what eid means or enumerate the valid role values. Since schema coverage is only 50% and there are no enums, the description only partially compensates for the missing parameter documentation.

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 title and description clearly identify this as the hackathon roster read tool, with a specific verb ('Read') and resource ('roster'). It further distinguishes itself by detailing role-specific views, so an agent can tell it apart from sibling tools like ic_hack_get or ic_hack_results.

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 gives strong role-based usage context and explicitly lists required scopes for each role group. It does not name specific alternative tools or state when not to use it, but the role scope and view definitions effectively guide an agent on appropriate invocation.

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