list_assignments

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

No annotations are provided, so the description must fully disclose behavior. It mentions pagination and return fields but omits whether the operation is read-only, any rate limits, required permissions beyond authentication, or side effects. For a list operation, this is minimally 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 a single sentence that contains all essential information (verb, resource, scope, pagination) without fluff. Every word earns its place.

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?

For a simple paginated list tool with 2 parameters and no output schema, the description is adequate but incomplete: it does not specify ordering, filters (e.g., status), or whether all assignments or only active ones are returned. The stated return structure (data, total, page, limit, totalPages) is 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?

Schema description coverage is 100% (both page and limit have descriptions with defaults). The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 assignments (call tasks) for the authenticated user with pagination,' providing the specific verb (list), resource (assignments/call tasks), and scope (for authenticated user). It distinguishes itself from siblings like get_assignment (singular) and create/delete actions.

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 does not provide when-to-use or when-not-to-use guidance, nor does it mention alternatives among sibling tools (e.g., get_assignment for a single item). The only context is 'for the authenticated user,' but no exclusion criteria or comparison.

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