list_initiatives

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

Annotations indicate readOnlyHint=true and openWorldHint=true, and the description adds that a ToolError is raised when the initiatives feature is disabled. However, it does not discuss pagination behavior or potential large response sizes beyond the open world hint.

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 concise but includes a docstring-like breakdown (Args, Returns, Raises) that adds structure. The main sentence is front-loaded, though the docstring format is slightly verbose for a tool description.

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 presence of an output schema and annotations, the description covers the error case and implies pagination via parameter examples. It is reasonably complete but could mention pagination behavior explicitly.

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 parameter 'params' has 0% schema description coverage, but the description elaborates with 'Optional query parameters as a dictionary (e.g., per_page, cursor)', adding meaningful context beyond the empty schema definition.

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 all initiatives in a workspace,' specifying the verb (list), resource (initiatives), and scope (all in workspace). It is distinct from siblings like create, retrieve, update, delete.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives such as list_initiative_projects or retrieve_initiative, nor does it specify prerequisites or limitations.

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