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

The description adds behavioral context beyond the annotations by stating execution is synchronous, task support is forbidden, and the returned JSON is internal application state. It also specifies response-handling rules (never display raw JSON, mention IDs selectively). These are useful traits not captured by the readOnly/idempotent/not-destructive hints. However, it does not disclose error behavior or the nature of template data beyond being internal state.

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 run-on sentence containing several instructions. It redundantly repeats 'Classification: read-only,' which is already in annotations, and includes a mix of tool purpose and global orchestration rules. It is not excessively long but lacks clear structure and could be tightened to separate purpose from response guidelines.

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?

Despite having an output schema, the description is incomplete for an 11-parameter tool with no parameter documentation. It does not explain what a template is, when to fetch it, or how the returned internal state should inform the assistant's response beyond vague formatting rules. The description leaves major gaps in domain context.

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%, and the description provides absolutely no explanation of any of the 11 parameters. Even the required templateId is undocumented in both the schema and description. The description does not compensate for the missing parameter semantics, leaving the agent to guess which IDs are needed and how they relate.

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 simply restates the name 'get template' without adding any specificity about what a template is or what getting it accomplishes. It does not distinguish this tool from siblings like list_templates or get_asset. The phrase 'internal application state' is vague and does not clarify the resource.

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?

No guidance is provided on when to use this tool versus alternatives. The only usage-related instruction is 'Use assistantSummary first when responding to the user,' which is a generic response rule, not a tool-selection criterion. There is no mention of prerequisites or scenarios where this tool is preferred.

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