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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and side-effect profile is covered. The description adds only the 'tracked' qualifier and workspace scoping; it says nothing about pagination, ordering, or how archived competitors are handled even though include_archived exists.

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?

A single front-loaded sentence with no filler, which makes the tool's purpose immediately clear. It is efficient, though its brevity is also the source of the missing usage and parameter detail.

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 simple read-only list tool whose annotations already convey the safety profile and with no output schema to explain, the description is minimally adequate. However, it omits filtering behavior (brand_id, include_archived) and any sense of result shape, which leaves gaps for a 4-parameter tool.

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 description coverage is only 50%: workspace_id is well documented in the schema, but brand_id and include_archived have no descriptions anywhere, and the description adds no meaning for either. With two of four parameters undocumented, the description fails to compensate for the coverage gap.

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 tracked competitor domains') and scopes it to the workspace, so an agent understands exactly what it returns. It does not explicitly contrast with the inverse sibling aidelly_add_competitor, but the action distinction is obvious from the verb.

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?

There is no guidance on when to use this versus alternatives (e.g., aidelly_list_creators, aidelly_get_brand_profile) or on prerequisites such as whether a workspace_id or brand_id is needed to get meaningful results. Usage is only implied by the verb 'List'.

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