Omiss Officers

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

No annotations are provided, so the description carries the burden. It does disclose the return shape (sections, each with people carrying role, callsign, name, OM number), which gives useful read-oriented context, but says nothing about permissions, rate limits, or whether the roster is static or current. For a low-risk no-param listing, this is acceptable but not rich.

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 lines, front-loaded with the resource scope and followed by the return structure. Slight overlap with the declared output schema, but no filler sentences.

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?

With no inputs and an output schema present, the description only needs to establish scope, which it does by enumerating the categories of people returned. It is complete enough for an agent to call it correctly, with only marginal benefit remaining for auth/sibling 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?

The tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no input is needed and spends its words on output content instead.

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?

States a specific verb ('List') and a clearly bounded resource (OMISS officers, directors, band coordinators, committees, appointees, past presidents, VIPs). An agent can tell this apart from omiss_member_lookup or omiss_net_checkins by the roster-of-officials scope, though it never explicitly names a sibling.

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?

Usage is implied by the content — you call it to get organizational leadership rosters — but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as omiss_member_lookup for individual members. Adequate but leaves routing to inference.

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