metadata_get_user_metadata

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

With no annotations, the description carries the full burden. The 'GET' verb implies a read, but it says nothing about authentication, what happens when a userId has no metadata, or the response shape, and there is no output schema to fall back on.

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?

Very short and front-loaded, but 'Tags: Metadata Controller' and the raw path template are scaffolding rather than useful description text. Nothing is misleading, yet the brevity here reflects under-specification as much as efficiency.

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 read tool with no annotations and no output schema, the description omits the return-value behavior, error/empty-metadata semantics, and auth requirements that an agent would need. Given the complexity signals, it is materially incomplete.

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 userId parameter; the only hint is the {userId} path placeholder, which merely restates the schema name. Nothing explains the format, range, or that it references an existing user, so the description does not compensate for the coverage gap.

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 specific verb ('Get') and resource ('user metadata') scoped to a userId, which distinguishes it from metadata_get_node_metadata and metadata_upsert_user_metadata by name. It does not explicitly contrast with those siblings, but the intent is unambiguous.

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?

No guidance on when to use this versus metadata_get_node_metadata or metadata_upsert_user_metadata, and no prerequisites (e.g., that the user must exist or that metadata is optional) are stated. The agent is left to infer context entirely.

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