task_list

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

The description explicitly marks the operation as [READ], explains pagination behavior via returned/limit/truncated fields, and describes the effect of the limit parameter. Given no annotations, this is comprehensive behavioral disclosure.

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 paragraph with clear front-loading: first line states purpose and returned fields, followed by concise bullet-like explanations for each parameter. No wasted words.

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 tool with 3 simple parameters, no required fields, and no output schema, the description covers the purpose, parameter semantics, and return behavior thoroughly. It mentions the returned fields and truncation, making it complete.

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?

With 0% schema description coverage, the description fully compensates: it gives examples for status (RUNNING, SUCCEEDED, FAILED), explains limit's default and reporting behavior, and clarifies target as a config-based parameter. This adds significant meaning beyond 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 lists tasks from Prism Central with specific fields (extId, operation, status, %complete, entity). It is a specific verb+resource and distinguishes from sibling list tools by focusing on tasks.

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 optional filters (status, limit, target) with examples and explains the default limit and truncation behavior. It does not explicitly state when not to use or list alternatives, but the context is clear for task listing.

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