abx_get_all_action_templates

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the description adds nothing about safety. It also says nothing about collection size, pagination, filtering, or ordering — the behaviors that actually matter for a 'fetch all' endpoint. The three lines merely restate the same fact plus the raw HTTP path.

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?

Three lines that repeat the identical idea ('Fetch all action templates' / 'Retrieves all action templates') plus the HTTP path. Only one sentence of content is present; the rest is duplication with no front-loaded added value.

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?

Annotations cover the read-only safety profile and there is no output schema or parameters to explain, so the basics are covered. However, for a 'get all' collection endpoint, an agent would benefit from knowing whether the response is paginated or how large it can be, and none of that is disclosed.

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 tool takes zero parameters and the schema is fully specified, so there is nothing for the description to clarify. Baseline 4 applies for a no-parameter tool.

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: fetch/retrieve all action templates, and the endpoint path confirms it is a collection read. It is implicitly distinguishable from the sibling abx_get_action_template_by_id, but the description never names that sibling to make the contrast explicit.

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 when-to-use or when-not-to-use guidance. The only signal is the word 'all', which weakly implies 'use this for the full collection rather than a single template', and no mention is made of the obvious alternative abx_get_action_template_by_id.

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