list_initiatives

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

The description is consistent with annotations (readOnlyHint true, destructiveHint false) and adds no contradictions. However, it provides no additional behavioral context beyond what the annotations already declare, such as pagination, data scoping, or response format. The annotations carry the safety burden, so a baseline score is acceptable.

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 one concise sentence that clearly states the action and scope without any unnecessary words. It is front-loaded and 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?

The tool is simple and annotations confirm a safe read operation, but the lack of parameter documentation and absence of an output schema leave some ambiguity about the optional 'params' argument. The description is minimally adequate for a basic list operation but does not fully address potential usage details.

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 input schema has a single generic 'params' object with no documented properties and 0% schema description coverage. The description 'List all initiatives' offers no parameter information, leaving the agent with no guidance on optional filters, pagination, or other possible arguments. Since schema coverage is 0%, the description must compensate but fails to do so.

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 uses a specific verb 'List' and resource 'initiatives' with workspace scope, clearly identifying the operation. It distinguishes from sibling tools like create_initiative, retrieve_initiative, update_initiative, and delete_initiative by stating the list action.

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 provides no guidance on when to use this tool vs alternatives such as retrieve_initiative or search_work_items. There is no mention of exclusions, prerequisites, or comparison with other list tools, leaving the agent without explicit usage context.

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