metadata_user_get

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 covered. The description adds nothing beyond that: no indication of which metadata namespace, whether the result is arbitrary key/value pairs, or how it relates to metadata_node_get. It does not contradict annotations, but it contributes no additional behavioral context.

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?

Three words, front-loaded and free of redundancy, but the brevity here reflects under-specification rather than disciplined conciseness. It is appropriately sized only in the sense that there is nothing extraneous to cut.

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 no output schema, the description carries the burden of explaining what metadata is returned (free-form key/value store? fixed fields?), and it does not. For a lookup tool whose result shape is opaque and whose id convention is ambiguous among many similar sibling tools, this is inadequate.

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 coverage is 0% and the single parameter userId is only implied by 'user'. The description does not state that userId identifies the target user, nor whether it is a numeric internal ID versus a UUID or username, which matters given siblings like users_get_by_username and users_get_by_short_uuid.

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?

"Get user metadata" is nearly a verbatim restatement of the tool name metadata_user_get, with no scope, no field list, and no differentiation from sibling reads like metadata_node_get or users_get. An agent cannot tell what 'metadata' means here or how it differs from user profile fields returned by users_get.

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 mention of when to prefer users_get or metadata_user_upsert, and no prerequisites such as permission requirements. The agent must infer everything from the name alone.

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