Get template

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

With no annotations present, the description carries the behavioral burden. It communicates that this is a read operation (get) and that the result includes Meta approval status, which is useful. However, it does not disclose authentication needs, error behavior, or response format implications.

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 a single, front-loaded sentence with no filler. It communicates the core operation and a valuable extra detail compactly.

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 get-by-id tool with one required parameter, the description is mostly adequate. However, with no output schema and no mention of response shape or where the template ID comes from, an agent still has meaningful gaps that the description does not close.

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%, so the description must compensate for the undocumented templateId parameter. 'By id' merely restates the parameter name and does not explain the ID format, its origin, or how it relates to other template operations. This is insufficient for a low-coverage schema.

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 operation ('Get a single template by id') on a clear resourceressing. The phrase 'including Meta approval status' adds a distinctive detail that separates it from generic listing tools and other getters. It is unambiguous and immediately tells an agent what this tool does.

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?

'Get a single template by id' clearly establishes that this tool is for retrieving one specific template when the caller has a templateId. It does not explicitly name alternatives like list_templates or get_template_variables, but the singular 'by id' condition makes the intended use clear.

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