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

Annotations only declare readOnlyHint=true, and the description adds substantive context beyond that: the exact shape of returned records and the underlying endpoint (GET /ticket-options). It does not discuss pagination semantics or whether options are organization-wide or location-scoped, keeping it out of 5 territory.

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?

One dense sentence stating purpose, return fields and the downstream dependency, plus a short endpoint reference. Nothing is redundant and the most decision-relevant information (what you get, why you need it) is front-loaded.

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 output schema, the description usefully names the returned fields, and the schema fully covers the paging controls, so an agent can call this correctly. The one unaddressed nuance is scope (global vs. per-location/per-organization options), which prevents a perfect score.

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?

All three parameters (limit, cursor_next, cursor_prev) are fully documented in the schema with descriptions and bounds, so the description carries no additional parameter burden. Baseline 3 is appropriate when schema description coverage is 100%.

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 and resource ('List the helpdesk ticket options') and enumerates exactly what is returned — configured types, priorities and severities with _id, category and label. This is clearly distinguishable from the sibling officernd_list_tickets, which lists actual tickets rather than configuration values.

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?

Explicitly routes the agent: 'Their _ids are required by officernd_create_ticket,' which tells the caller when this must be invoked ahead of ticket creation. It stops short of stating any exclusions or contrasting conditions for the other list_* siblings, so a 4 rather than a 5.

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