apply_template_overrides

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

Annotations are effectively all false, providing no safety profile, so the description carries the full burden. It states the action ('apply') but does not disclose side effects, whether existing overrides are overwritten, whether the operation is reversible, or what the response indicates. The two-mode behavior is present, but the consequences are opaque.

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 one efficient sentence that front-loads the core behavior and the two invocation modes. It contains no filler, though its brevity sacrifices useful detail for the sake of conciseness.

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 mutation tool with no output schema and mostly absent annotations, this description is too thin. It does not explain what 'applying' does to the target, what valid override_type values exist, how conflicts are handled, or what a successful invocation returns. An agent would likely need additional context to invoke it confidently.

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 only 50%, and the existing parameter description ('Entity ID') is tautological. The description clarifies that entityId refers to a template instance and that overrides can be a specific subset, but it does not explain the meaning of resource_id, override_type, or path, leaving substantial semantic gaps.

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 names a specific action ('Apply') and resource (template instance overrides), and clarifies that it either applies all overrides or only the supplied override records. It is clear and informative, though it does not explicitly name sibling tools like get_template_overrides or revert_template_overrides to distinguish itself.

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 guidance on when to use this tool versus alternatives such as get_template_overrides, revert_template_overrides, or unlink_template_instances. It implies two invocation modes but lacks contextual conditions or exclusions.

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