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

The description adds no behavioral context beyond what annotations provide (readOnlyHint=false, etc.). It does not disclose side effects, authorization needs, or what 'ai-draft' entails. Annotations carry all behavioral information, but the description fails to enrich it.

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 under-specified, not concise. Every sentence should add value; this single line is just the endpoint path and provides no actionable 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?

Given the complexity (6 params, no output schema, many siblings), the description is completely inadequate. It fails to explain what the tool does, its relation to inbox items, or how it differs from similar tools.

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?

With only 50% schema description coverage, the description should compensate but does not. It adds zero information about the 6 parameters, leaving the agent to rely solely on the schema (which itself has gaps, e.g., 'id' and 'idempotency_key' lack descriptions).

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 is merely the HTTP endpoint 'POST /inbox/items/{id}/ai-draft', which restates the tool name without explaining what the tool does. It fails to specify any action or resource, making it useless for an AI agent to understand the tool's purpose.

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 guidance is provided on when to use this tool versus alternatives like aidelly_post_inbox_items_id_respond. There are no prerequisites, exclusions, or context for appropriate invocation.

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