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

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by disclosing what the listing includes: installed templates, newer-version indicators, and plan/installs left, plus the reinstall route.

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 tight sentences with the core listing behavior front-loaded. The second sentence earns its place by routing the update action to install_template.

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 zero-parameter, read-only listing tool with no output schema, the description gives enough return-content context and the relevant follow-up action. It could be slightly more complete by clarifying pagination or the exact shape of the plan/installs-left data, but the essential information is present.

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?

There are zero parameters, so parameter semantics are not a meaningful differentiator. The baseline for a no-parameter tool is 4, and the description does not need to explain parameter meanings.

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 uses a specific verb, "List," and a precise resource/scope: templates installed by this Boterly account. It also distinguishes the result set by mentioning newer-version status and plan/installs left, and it names install_template for the related update action.

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?

It gives clear guidance for the update path by saying to reinstall with install_template, but it does not explicitly say when to use my_templates versus search_templates or diagnose_problem. The intended use is implied by "installed" rather than stated with alternatives.

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