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

The description adds no behavioral context beyond what annotations already provide. Annotations indicate write, non-idempotent, non-destructive, but the description says nothing about side effects, permissions, or scope of changes.

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 extremely short but fails to be informative. Conciseness is undercut by under-specification; it is not appropriately sized for the tool's complexity.

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?

Given no output schema, high parameter count, nested objects, and complex domain (content automations), the description is completely inadequate. It does not explain return values, side effects, or parameter relationships.

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?

The description adds no meaning beyond the input schema. Schema coverage is 60% with generic descriptions for 'body' and 'query'; brand_id and idempotency_key lack descriptions. The tool description should compensate but does not.

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 'POST /content-automations' is a tautology of the endpoint and HTTP method, providing no verb-resource statement. It fails to explain what the tool does, and does not distinguish it from siblings like aidelly_create_post or aidelly_post_content_automations_id_trigger.

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 usage guidelines are provided. The description lacks any indication of when to use this tool versus alternatives, such as aidelly_create_scheduled_post or aidelly_get_content_automations.

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