list_actions

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

No annotations are provided, so the description carries the transparency burden. It states it's a list operation (implying read-only) but doesn't explicitly mention side effects, error conditions, or whether all actions are returned. Given the minimal nature, it's adequate but not fully transparent.

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 concise sentences that cover the tool's purpose and pagination details without any redundancy or fluff. It is well-structured and easy to parse.

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?

There is no output schema, so the description must hint at the return structure. It mentions `next_offset`, suggesting the response includes a pagination token, but doesn't describe the full response format. Given the simplicity of a list operation, this is sufficient, though slightly more detail would be helpful.

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 description adds significant meaning to the parameters: it explains the `limit` cap and default, and how `offset` should be used with `next_offset` for pagination. This goes well beyond the schema's simple type/default definitions, fully clarifying the intended usage.

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 'List API actions exposed by OpenProject.' This provides a specific verb (list) and resource (API actions), and distinguishes it from sibling tools that list specific resources like grids, categories, or projects.

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 explains pagination behavior ('limit is capped at OPENPROJECT_MAX_PAGE_SIZE (default 50); pass the returned next_offset as the next call's offset') which indicates when to use it (to enumerate all actions) and how to handle large result sets. It doesn't explicitly contrast with alternatives, but the purpose is clear enough.

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