get-work-order-tasks

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

The description discloses it is a read operation ('Get'), but with no annotations, it should provide more behavioral details such as whether it returns all tasks, pagination, or ordering. It does not address these aspects.

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 of five words, making it very concise. However, it could add useful context without becoming verbose, so it scores slightly above average.

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?

Given no output schema, the description should at least indicate the return type (e.g., a list of tasks). It only states the basic purpose, leaving significant gaps about the response structure.

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 coverage is 100%, and the description adds 'for a specific work order', which clarifies the parameter's role but largely repeats the schema's description. The added value is minimal, meeting the baseline.

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 the verb 'Get' and the resource 'tasks for a specific work order', which precisely defines the tool's function. This distinguishes it from sibling tools like 'add-work-order-task' and 'get-work-order'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or context, leaving the agent to infer usage from the name alone.

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