yaaif_approval_strategies_list

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

No annotations are provided, so the description must disclose behavioral details. It only states the action and resource, omitting any information about pagination behavior, default limits, or whether the list is scoped to the current tenant. This is a significant gap for a list endpoint.

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, clear sentence that is appropriately concise and front-loaded. It conveys the core purpose without any wasted words, which is efficient.

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 tool references 'approval-service' and has pagination parameters, the description is incomplete. It lacks return format details, pagination semantics, and any contextual hints about the approval strategies domain. An agent would need more to use this correctly.

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 mention the 'limit' and 'offset' parameters at all. The agent cannot infer that these are for pagination, and despite the parameters being optional with no enums, the description fails to compensate for the lack of schema documentation.

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 action ('List') and the resource ('approval strategies'), which distinguishes it from the sibling tools like yaaif_approval_strategy_get and yaaif_approval_strategy_create. It is concise and unambiguous, though it does not explicitly differentiate from other list tools.

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?

The description implies the tool is for retrieving a list of approval strategies, which is clear from the verb 'List'. However, it does not specify when to use this over the get, create, or publish sibling tools, nor does it mention any prerequisites (e.g., required authentication or tenant context). It provides minimal context for tool selection.

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