Theme Breakpoint Create

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no permission requirements, no idempotency/duplicate behavior, no statement of what state is mutated. The verb 'Add' at least signals a write operation, which is the only behavioral signal present.

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 single fragment is short but this is under-specification rather than conciseness; there is no front-loaded structure because there is essentially no content to structure.

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?

For a 7-parameter mutation tool with no annotations and 0% schema coverage, the description is far too thin. The presence of an output schema excuses it from explaining return values, but it still omits parameter meaning and preconditions entirely.

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% across 7 parameters, so the description must compensate and it does not. It says nothing about machine_name vs breakpoint_id (a confusing near-duplicate pair), label, media_query syntax, weight, multipliers, or the optional path.

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?

"Add a breakpoint to theme" gives a recognizable verb (Add) and resource (breakpoint) scoped to a theme, so the basic operation is inferable. However, it does nothing to distinguish this from the many sibling theme_* mutation tools (theme_region_create, theme_library_create, theme_create) beyond the resource noun, and 'breakpoint' is never defined.

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 guidance on when to use this tool versus alternatives, no prerequisites (must a theme exist? must it be the active theme?), and no mention of what happens if a breakpoint with the same machine_name/breakpoint_id already exists.

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