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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that results are paginated, without explaining the cursor-vs-offset mechanism or default page behavior, so it adds modest value beyond structured data.

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, well-formed sentence with the resource and scope front-loaded and no filler. It is efficient, though its brevity leaves substantive gaps rather than being genuinely complete.

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 six-parameter, low-coverage list tool with no output schema, the description omits the pagination contract (which of cursor/offset to use and in what order), the meaning of brand_id/workspace_id scoping, and the purpose of the query override. An agent could call it, but would likely guess at pagination semantics.

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 33%, so the description is expected to compensate, and it does not: the interplay of limit, cursor, offset, brand_id, and the opaque "query" override object is left entirely to the schema. "With pagination" gestures at two of the six parameters without explaining them.

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?

States a specific verb and resource ("List all reports") plus scope ("in the workspace"), so an agent can immediately tell it apart from aidelly_get_report (single item) and aidelly_list_report_links. It does not, however, differentiate itself from other list endpoints or note what a "report" covers.

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 when-to-use guidance, no mention of alternatives such as aidelly_get_report for a single report, and no prerequisites. "With pagination" hints at how to call it, but not when to prefer this over sibling list tools.

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