list_tasks

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

No annotations are provided, so the description bears the full burden. It hints at read-only behavior ('list') and filtering, but does not explicitly state safety, side effects, or required permissions. The lack of disclosure on property specification adds ambiguity.

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, concise and to the point. It contains no unnecessary words or repetition, earning its place with no fluff.

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?

The description covers the basic purpose and filtering, but lacks details on output format, pagination, ordering, or how to specify the property. Given no output schema and a single sentence, the agent may lack sufficient information to use the tool correctly.

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?

Although the input schema has no defined parameters (only additionalProperties: true), the description mentions four filter dimensions: status, assignee, taskbox, search. This provides meaningful semantics that the schema alone lacks, helping the agent understand possible arguments.

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 that the tool lists all SEO tasks for a property and can filter by status, assignee, taskbox, or search. It distinguishes from siblings like get_task (single task) and create_task. However, it does not specify how the property is identified, which could be ambiguous.

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 like get_task or list_tags. The description does not mention exclusions or prerequisites, leaving the agent without clear selection criteria.

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