Service Templates

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context about data volume ('holds hundreds') and substring filtering, which helps an agent anticipate large result sets. It does not contradict the annotations.

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 two sentences, front-loaded with the core purpose and followed by practical filtering guidance. It contains no filler and avoids repeating information already present in the schema or annotations.

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 simple read-only listing tool, the description combined with full parameter documentation, rich annotations, and an output schema is sufficient for correct selection and invocation. The only minor omission is explicit naming of sibling alternatives, but that is not necessary for calling this tool correctly.

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%, so limit and name_filter are already well-documented. The description reinforces the purpose of name_filter but does not add substantial meaning beyond the schema, so the baseline score is appropriate.

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 action ('Find'), a clear resource ('service templates'), and explains what service templates are ('reusable check/notification configurations for services'). It also includes the key search behavior via name_filter, clearly distinguishing this from sibling list tools by resource type.

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 practical context for when to use name_filter: 'An instance holds hundreds; pass name_filter with a substring to narrow the result.' It clearly communicates the filtering workflow, though it does not explicitly mention alternatives or exclusions relative to sibling tools like list_servicetemplategroups.

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