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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description goes further by explaining what the returned config actually means (enrichment mapping of provider fields to CRM fields, and whether an existing value may be replaced) and why that determines dispatch overwrite behavior. It omits error cases such as an unknown template_id or mismatched connection.

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 sentences, front-loaded with what is returned and followed by the reason to call it. The second sentence is long but every clause carries meaning about overwrite semantics; nothing is filler.

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?

No output schema exists, so the description correctly takes on the burden of describing the return value (full template config, rule contents, mapping semantics). For a two-parameter read tool this is nearly complete; only failure modes and identity of the returned fields' naming are left implicit.

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% and both parameters are documented in the schema, including the prerequisite ordering ('Call list_rule_templates first'). The description adds no parameter-level syntax or format detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource (read one rule template) and clarifies scope by contrast: 'the actual rules, not just its name and kind.' This distinguishes it from the list/create/update/delete siblings, though it never names list_rule_templates directly.

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?

Gives a clear, actionable when: 'Read this before naming a template in a run, to see what the run would really do.' The condition for use is explicit, but no alternative (e.g. list_rule_templates for browsing) is named to route the agent away when a full config isn't needed.

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