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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds meaningful context beyond that: the fixed page size of 100 and the underlying endpoint GET /reports/ilt/{program_id}/, which signals the report scope is a single program. It stops short of describing pagination termination behavior or rate limits.

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?

Three short sentences that front-load the return payload, then filtering, then paging and endpoint. No filler, and the most decision-relevant information (what columns you get) comes first.

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 15-parameter, output-schema-less report tool, enumerating the returned fields is exactly the right compensating move. The description is nearly complete; the only real gap is routing guidance versus the other ILT listing tools, which matters given how many siblings exist.

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 67% schema description coverage, the schema already documents page, status, user_filter, session_name and the date bounds thoroughly. The description's mention of users/status/session/dates aligns with those parameters but adds no syntax or semantics beyond them, and it says nothing about method_earned, count_only, or the meeting-count range filters.

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 names a specific resource (attendance and results of one ILT program) and enumerates the returned columns, so an agent knows exactly what data comes back. It implicitly distinguishes itself from siblings like axislms_list_ilt_sessions or axislms_list_user_ilt_sessions by being a program-scoped report, but it never names those alternatives explicitly.

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?

'Filter by users, status, session and dates' gives implied usage context for narrowing results, but there is no explicit guidance on when to choose this over axislms_list_ilt_completions, axislms_list_user_ilt_sessions, or axislms_get_ilt_program. The agent must infer the selection criteria from the tool name alone.

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