get_user_metadata

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the REST route and '[READ]' tag, which restates the annotation rather than contributing new behavioral context like auth requirements or response shape.

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?

Two short lines with no padding; the resource name leads. It is tight, though the second line is essentially a restatement of the annotation.

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?

There is no output schema, so the description carries the burden of indicating what 'metadata' contains, and it says nothing. For a tool whose entire value is the payload it returns, this leaves the agent unable to judge relevance.

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 100% for the single userId parameter, so the baseline is 3. The description's ':userId' path notation adds no meaning about whether the value is a numeric id, short UUID, or username, which matters given the sibling resolve_user/get_user_by_short_uuid tools.

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+resource pair 'Get user metadata' is stated plainly, but 'metadata' is never defined, so an agent cannot tell what is actually returned. It also fails to distinguish itself from close siblings such as get_user_by_id, get_metadata, or get_node_metadata.

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 description gives no when-to-use context and names no alternative, despite a very crowded sibling set containing multiple user- and metadata-oriented getters. An agent must guess between this and get_user_by_id or get_metadata.

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