select_template

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'load into memory,' implying a state change but does not clarify side effects, authorization needs, or what happens to the previously loaded template. This is a significant omission for a state-mutating operation.

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 short sentence, which is concise but under-specified. It conveys a minimal purpose but lacks structure or detail that would help the agent understand the tool's role. It feels like a placeholder rather than a well-crafted description.

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?

Given the large set of sibling tools and the tool's stateful nature, the description is far from complete. It does not explain the effect of loading, the difference between this and similar tools, or any prerequisites. With one parameter and no output schema, the agent needs more information to call it correctly, which is missing.

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 has 0% description coverage, and the description does not explain the templateId parameter beyond its existence. No format, semantics, or constraints are provided, leaving the agent without useful guidance for filling in the required field.

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 the action 'select template' and what it loads (Schema/extra/table into memory), which is a specific verb and resource. However, it does not distinguish itself from the many sibling tools like get_template_detail or get_schema, and the term 'extra/table' is vague without further context.

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?

There is no guidance on when to use this tool versus alternatives. No mention of scenarios, prerequisites, or exclusions. The agent is left to infer from the name alone, which is insufficient.

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