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 fully covered. The description adds only the word 'metadata', hinting the payload is descriptive rather than the document content — a small but real contribution. It says nothing about behavior on a missing or unauthorized resourceId, which annotations do not cover.

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?

Four words, zero waste, front-loaded — but the brevity is under-specification rather than economy. It fits on one line yet omits routing and parameter facts an agent needs before the first call.

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?

An output schema exists, so the description need not explain return values, and the annotations cover the safety profile. However, a single-record getter in a family of sixty-plus get_* siblings needs at least a pointer to the ID source and a contrast with download_resource; both are absent.

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?

There is exactly one parameter, resourceId, and schema description coverage is 0% — the schema supplies only a pattern and length bounds, never what the ID refers to or how to obtain it. The description does not compensate: it never mentions resourceId, its format, or where IDs come from (e.g., list_resources).

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 verb 'Read' and the object 'resource metadata' identify the operation, but the description never distinguishes this from near-identical siblings such as list_resources or download_resource. An agent cannot tell from this text alone whether get_resource returns a single record, a metadata envelope, or the file itself.

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 statement, no prerequisite, and no named alternative ('use download_resource for the file body'). The agent must infer routing from the tool name and the required resourceId alone.

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