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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on error behavior for an unknown id, no indication of what the registry lookup returns, and no added context for the closed-world scope.

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?

It is a single short sentence with no filler, which is structurally clean. The problem is under-specification rather than verbosity, so it earns only a middling score.

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 tool with one undocumented parameter, no output schema, and a sibling set of seven shortcut-related tools, the description should at minimum say what a 'source' is and how it relates to lookup_shortcut/get_app_shortcuts. None of that is present, so an agent lacks the context to call it correctly.

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% for the single required 'id' parameter, so the schema does not say whether it is a shortcut id, an app id, or a registry key. The description mentions 'provenance registry metadata' but never explains what the id identifies, leaving the parameter's meaning unstated in both places.

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 verb (Read) and a resource (provenance registry metadata), so it is more than a tautology. However, 'official provenance registry' is undefined, and nothing distinguishes it from siblings like lookup_shortcut or get_app_shortcuts — an agent cannot tell what a 'source' is here.

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 when-to-use guidance, no prerequisite, and no mention of the alternatives in the sibling set (lookup_shortcut, get_app_shortcuts, list_apps). The agent must guess which tool retrieves which kind of record.

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