list_helpdesk_levels

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

No annotations exist, so description carries burden. It implies a read-only list operation but does not confirm safety, side effects, or permissions. The 'include_deleted' parameter hints at mutation in reading deleted records, but not fully disclosed.

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 concise sentence, front-loaded with the main action ('List active help desk levels') and optional variant ('or one in particular by ID'). No wasted words.

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 no annotations or output schema, the description lacks details on response structure (e.g., fields returned, pagination, ordering). For a list tool with two parameters, more context is needed for correct usage.

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?

With 0% schema description coverage, the description adds meaning: 'or one in particular by ID' explains level_id's purpose, and 'active' combined with include_deleted clarifies default behavior. However, it doesn't specify parameter types or exact effect of include_deleted.

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 clearly states the tool lists help desk levels, with optional filtering by ID. It distinguishes from siblings like list_helpdesks_and_levels (which lists both helpdesks and levels) and list_level_observers.

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 (e.g., list_helpdesks_and_levels, list_level_observers). No mention of prerequisites or exclusions.

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