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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds useful behavior context by naming the returned payload (attachments, activity history), but it says nothing about permissions, scoping quirks, or failure modes.

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; the primary payload is stated immediately. It is efficient but very thin for a tool with four parameters.

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 read-only tool with annotations covering safety and no output schema, the description is adequate but leaves the undocumented `id`/`brand_id` parameters and workspace scoping unexplained. Given the sparse schema, a bit more on the identifying parameter and scoping would complete it.

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%: `id` and `brand_id` are undocumented in the schema, and the description adds no parameter meaning at all. The `id` (uuid) and workspace/brand scoping semantics are never explained, so 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?

States a specific verb and resource ('Get full details of a task') plus the scope of the payload (attachments and activity history), so it is clearly distinguishable from the related list_tasks at a glance. It does not explicitly name siblings like aidelly_list_tasks or aidelly_get_post to disambiguate further.

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 call this versus alternatives such as aidelly_list_tasks (to enumerate) or aidelly_get_post. No prerequisites or context are given, leaving the agent to infer usage entirely.

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