mdl_awards_list

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no mention of whether results are paginated, user-scoped, cached, or how large the result set may be. With annotations doing all the work, the description contributes no incremental behavioral context.

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?

At two words it is certainly short, but this is under-specification rather than conciseness — the fragment earns its place only by naming the resource. There is no front-loaded statement of purpose or scope to structure around.

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 zero-parameter, read-only list tool with no output schema, the description should at minimum say what an "award" is in this domain (e.g., per-title awards, user achievements) and whether the full list is returned. None of that is present, leaving the agent unable to predict the response shape.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description does not mislead about inputs (it correctly implies no filtering arguments are accepted).

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?

"Awards: list." is essentially a restatement of the tool name mdl_awards_list split into a noun and a verb. It does identify the resource (awards) and the operation (list), but adds no distinguishing detail — no indication of whose awards, what kind, or scope. This is tautological rather than descriptive.

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?

There is no guidance on when to use this tool, what preconditions exist, or how it relates to any alternative. The sibling list contains many list-style tools (mdl_comments_list, mdl_custom_lists_get_user_lists, mdl_notifications_fetch), and nothing here helps an agent choose among them.

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