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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the GET endpoint and resource clarification, but does not mention pagination behavior, return shape, auth requirements, or rate limits.

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?

Two short sentences with the core resource and filtering dimensions front-loaded; there is no wasted text.

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?

This is a moderate six-parameter list tool with no output schema, and annotations cover the read-only safety profile. The description identifies the resource and main filters but leaves sorting, pagination behavior, and return shape largely to the schema or inference.

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 67% schema description coverage, the schema already documents page, limit, assigned_user_id, and sort_dir. The description only names status and assigned_user_id as filters and adds little explanation for sort_by, sort_dir, or pagination beyond what the schema provides.

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 states a specific verb and resource ('List subtasks') and clarifies that subtasks are job checklist items, which helps distinguish the resource. It does not differentiate this list endpoint from sibling list/get tools such as fieldpulse_list_jobs or fieldpulse_get_job.

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 phrase 'by status or assigned user' implies that this tool is used for filtered subtask retrieval, but there is no explicit guidance on when to use it versus sibling tools, nor any when-not-to-use conditions or prerequisites.

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