update_meta

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

No annotations are present, so the description must carry the full behavioral burden. It lists updatable fields but does not state whether existing values are merged or overwritten, whether the operation is reversible, whether all listed fields are required in patch_fields, or what happens to unspecified fields. This is a significant transparency gap for a mutation tool.

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?

The description is a single, focused sentence with no filler. The action and target fields are front-loaded, making it easy to scan and understand.

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 a simple two-parameter shape, the description lacks behavioral details (merge vs. replace, field requirements), usage guidance, and any definition of slug. With zero annotations, an agent would still have to infer critical invocation semantics.

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?

The description adds meaning for patch_fields by naming the hero fields, and the schema already lists them in the patch_fields description. However, slug is undocumented in both the schema and the description, and patch_fields value types, optionality, and behavior with additionalProperties are not clarified. With 50% schema coverage, the description partially compensates but does not fully define the parameters.

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 description states a specific action ('Update the hero') and enumerates the target fields (title, subtitle, summary, repo links, setup command), which distinguishes it from sibling update tools like update_section or set_theme. However, the resource 'hero' is somewhat terse and doesn't clarify which site it applies to.

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 is given on when to use this tool versus alternatives such as update_section, set_theme, or other site-management siblings. There are no exclusions, conditions, or context triggers, only a statement of what the tool does.

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