oracle_tm_list_templates

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

No annotations are provided, so the description carries the full burden. It does not disclose behaviors such as pagination, rate limits, or what happens when no category is specified. The list of categories is given but without explaining the nature of the list (e.g., whether it is exhaustive or dynamic).

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 very short and to the point. However, it lacks structure such as separate sections for usage or examples. For a simple listing tool, this is acceptable but could be improved with explicit parameter guidance.

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 context of sibling oracle_tm tools, the description does not explain how listing templates fits into the threat modeling workflow (e.g., templates can be loaded with oracle_tm_load_template). The existence of an output schema is noted, but the description adds no workflow context. This leaves the agent uncertain about the tool's role.

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 clarify parameter usage. It lists categories but does not explicitly state that the 'category' parameter filters the list by those values. The mapping between the parameter and the category list is implicit, leaving ambiguity.

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 clearly states the verb 'list' and resource 'available threat model templates'. It lists categories, implying a filtering capability. It distinguishes from sibling tools like oracle_tm_load_template which loads a specific template. However, it does not explicitly state that the category parameter filters the list, slightly blurring the purpose.

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 on when to use this tool vs alternatives. The description does not mention prerequisites, conditions, or when not to use this tool. There is no contrast with similar tools like oracle_tm_load_template or oracle_tm_match.

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