create_metadata

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

Annotations already cover the core read/write/idempotent profile, and the description adds a useful caveat: the body fields are not static and must be discovered via GET or /schema. No other behavioral details like auth, error modes, or side effects are provided, so it earns a mid score.

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?

Tight and organized: action, endpoint, then args. No filler. However, the args section is so terse that it borders on under-specification rather than concise clarity.

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?

Despite an output schema, the description leaves the agent reliant on external endpoints to learn the body shape and gives no semantic for force_save. For a creation tool, it doesn't state response behavior or side effects, making it incomplete in context.

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?

With 0% schema coverage, the description should explain both parameters. For body it points to GET/schema for fields, which is helpful; for force_save it only repeats that it's a query parameter, adding no meaning beyond 'boolean'.

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?

Clearly states verb 'Create' and resource 'Metadata', reinforced by the explicit POST endpoint. It doesn't distinguish itself from siblings like create_metadata_test or create_metadata_action_by_name, but the core action 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 tool versus the many sibling create_* tools, no exclusions or alternatives. The only instruction is to consult GET/schema before constructing the body, which is about parameter discovery, not usage context.

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