List Possible Assignees (Company)

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

The description contains an inaccuracy: it states 'Returns a paginated JSON array of Workflows,' but the tool is about possible assignees, not workflows. This misrepresentation affects transparency. Annotations already indicate read-only and idempotent, so no contradiction.

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 and front-loaded with the purpose. Each sentence adds value, though the API endpoint line could be considered extraneous for an AI agent. Overall well-structured.

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 description covers pagination and required parameters, but it lacks details on the conditional tool_subtype parameter and does not clarify the response structure beyond 'paginated JSON array'. Given no output schema, more detail on return format would be beneficial.

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 100% coverage. The description adds minimal extra context by highlighting required parameters (company_id, tool_type) and pagination controls (page, per_page). It does not explain the conditional requirement for tool_subtype when tool_type is 'correspondence', which is in the schema.

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 it returns a list of possible assignees for a given company and tool, with specific use cases. However, it does not explicitly differentiate from the sibling tool 'list_possible_assignees_project', though the name implies company scope.

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 usage guidance: 'Use this to enumerate Workflows when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not mention when not to use or explicitly name alternatives, which would improve clarity.

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