get_template_overrides

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

Annotations already declare readOnlyHint=true, and the description's 'Read' aligns with that. The description adds the context that these are 'current apply/revert override records,' which is useful, but it does not disclose any additional behavioral traits such as empty results, error conditions, or effects on template instance state. No contradiction exists.

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?

A single sentence with no filler or redundant restating of the tool name. The key operation and resource are front-loaded, making it easy to scan.

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 single-parameter, read-only getter, the description is mostly complete: it names the resource, identifies the parameter semantics, and aligns with the readOnlyHint annotation. However, there is no explicit mention of what the returned override records look like, and no output schema exists to fill that gap, leaving a small amount of ambiguity.

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 schema describes entityId only as 'Entity ID' with a UUID format, which is vague. The description adds important meaning by clarifying that the entity ID refers to a template instance whose override records are being read, going beyond the structured schema information.

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 uses the specific verb 'Read' and names a clear resource: 'the current apply/revert override records for a template instance.' This distinguishes it from sibling mutation tools like apply_template_overrides and revert_template_overrides, even without naming them explicitly.

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 the tool is used to inspect override state for a template instance, but it does not explicitly state when to choose this tool over applying, reverting, or unlinking overrides, nor does it mention any preconditions. The read-only intent is obvious from the verb, but concrete usage guidance is absent.

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