Api managed documents templates retrieve

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds that results can be localized via a lang query parameter, which is genuine behavioral context, but says nothing about result size, ordering, or whether built-in and custom templates are mixed.

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?

Two short sentences, the action is front-loaded, and the optional parameter is noted second. Nothing is redundant or wasted.

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 listing endpoint with no output schema, the description should still hint at what a template record contains or how results are shaped. That gap, plus the lang parameter appearing in prose but not in the schema, leaves the definition slightly under-specified for an openWorld endpoint.

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 input schema is empty, so the description carries the entire parameter burden and does disclose an optional ?lang= query parameter that the schema omits. It does not state the accepted values or format for lang (e.g. ISO codes), leaving a small gap, but this is still meaningful added meaning over the 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?

States a specific verb and resource ('List available document templates'), which distinguishes it from the sibling ciso_assistant_api_managed_documents_list that deals with documents rather than templates. It does not explicitly name that sibling, so differentiation is inferable rather than spelled out.

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 call this versus the managed-documents list/create endpoints, nor any prerequisite or context. An agent must infer from the name alone that templates are a separate catalog used before instantiating documents.

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