get_tasks

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

Description implies a read operation but does not disclose side effects, authentication requirements, rate limits, or response format. With no annotations, it fails to provide sufficient behavioral context.

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?

Starts with a clear purpose, then uses concise bullet-point examples. No wasted words, efficient and scannable.

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?

Covers filtering and pagination well, but lacks return structure details (e.g., array of task objects). With no output schema, this is a gap. Adequate for basic usage but incomplete.

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?

Schemas have 0% description coverage. Description partially compensates with examples showing parameter usage, but not all 11 parameters are explained (e.g., milestone, types only mentioned). Adds context but incomplete.

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 'Get a filtered list of tasks with pagination,' specifying the action and resource. It distinguishes from sibling tools like get_task (singular) and create_task.

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?

Examples illustrate common filter combinations and pagination, guiding when to use. However, it does not explicitly exclude cases or name alternative tools for specific needs.

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