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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds only that lookup should be exact rather than approximate ('without guessing'), which is useful but minimal and does not cover return format, errors, or matching semantics.

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?

The single sentence is front-loaded and free of filler. It is efficient, though arguably under-specified for a three-parameter lookup operation.

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 three parameters, no schema descriptions, and no output schema, the description should clarify what keys, app, and platform mean and what an exact lookup returns. It omits app and platform entirely and gives no return expectations, so it is not complete enough for an agent to call confidently.

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?

Schema description coverage is 0%, so the description must compensate for three undocumented parameters. It only gestures at the 'keys' parameter and says nothing useful about 'app' or 'platform', leaving most parameter meaning unexplained.

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 verb ('look up') and vague resource ('keys'), but never explicitly says this is for shortcut keys or what kind of lookup result is returned. It also does not distinguish itself from siblings such as search_shortcuts or get_app_shortcuts.

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?

The phrase 'without guessing' implies exact-match lookup, giving a weak usage condition. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for fuzzy searching.

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