set_facts

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

Annotations already cover the safety profile: not read-only, idempotent, non-destructive, and open-world. The description adds useful behavioral context by stating that it creates the infobox or property group when it does not exist yet, but it omits permissions, side effects beyond creation, and removal behavior noted only in the schema.

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 tight sentences with no filler. The core action and location are front-loaded, followed immediately by the creation behavior.

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 a rich six-parameter schema, nested facts object, and annotations covering mutation safety, the description is largely complete for calling the tool. It could be stronger with usage guidance or explicit side-effect expectations, but no output schema exists and return values need not be explained.

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%, so the schema already documents all six parameters, including fact name/value semantics, null removal, case-insensitive updates, and target options. The description's examples slightly enrich understanding of facts but do not add parameter-level meaning beyond the schema.

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 verb ('Set'), resource ('facts'), and location ('infobox or resource sidebar'), with examples like Race, Age, Ruler, and Population. It is clearly not a generic page-writing tool, but it does not explicitly differentiate itself from siblings such as write_page or update_document.

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 explicit when-to-use guidance or alternatives. It explains what the tool does and that it creates the infobox/property group when missing, but an agent gets no instruction on when to prefer this over write_page, update_document, or other sibling tools.

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