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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the preview status and the extra response fields (viewer role + canReview flag). No contradictions or additional behavioral details like authentication or rate limiting are provided, which is acceptable given the annotations.

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 20 words, front-loading the HTTP method and endpoint, then stating the purpose concisely. No redundant information.

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 mentions the extra response data (viewer role + canReview flag) but omits details on pagination, sorting, filtering, or the full response shape. Although no output schema exists, a list tool would benefit from more contextual completeness. However, the preview label lowers expectations somewhat.

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 67% (workspace_id has a detailed description, query has a generic one, brand_id has none). The tool description does not add parameter-specific meaning beyond stating the scope ('current workspace'), so it does not compensate for the missing brand_id description. Baseline of 3 is appropriate.

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 'list posts pending sign-off for the current workspace', which is a specific verb+resource combination. It distinguishes itself from sibling tools like aidelly_list_posts (all posts) and aidelly_get_approvals (approval details) by focusing on pending posts and including the viewer role and canReview flag.

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?

The description does not provide guidance on when to use this tool versus alternatives such as aidelly_get_approvals or aidelly_list_post_approval_events. It mentions 'Public API preview' but does not elaborate on suitability or preconditions.

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