st.extension.configure

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add a meaningful behavioral requirement ('Requires confirm: true') that is not obvious from the schema alone. However, it does not disclose the mutating nature of the operation, whether settings are merged or replaced, what happens when the extension does not exist (despite an allowCreate parameter), or any side effects such as snapshots or reloads.

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 short sentences with no filler; the core action is front-loaded and the critical confirm requirement is stated immediately after. It is efficient, though brevity comes at the cost of omitting important parameter context.

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?

This is a complex tool with 8 parameters, nested objects, no output schema, and zero annotations, yet the description explains little beyond the surface action. An agent cannot correctly determine what unset does, how updates should be structured, what configKey selects, what allowCreate or snapshotLabel mean, or what the confirm flag actually gates. The description is inadequate for safe invocation of a tool with this many moving parts.

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%, so the description must compensate, but it only covers two conceptual areas: extension_settings (likely updates/configKey) and enabled state (enabled). Six other parameters (name, unset, confirm, allowCreate, snapshotLabel, and the nested updates object) are left completely unexplained. The description adds minimal meaning beyond the raw parameter names.

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 ('Configure') and a clear resource ('a frontend extension'), and it names the mechanism ('through extension_settings and/or enabled state'). This helps distinguish it from siblings like st.extension.install and st.extension.set_enabled, though it doesn't explicitly call them out. It is clear enough that an agent knows what resource this acts on.

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 implies that this tool is for configuring frontend extension settings or enabling state, which gives some context. The statement 'Requires confirm: true' is a genuine usage prerequisite. However, there is no explicit guidance about when to prefer this over siblings such as st.extension.set_enabled, st.config.patch, or st.character.configure, and no exclusions are stated.

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