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

Annotations only give the generic non-readonly/non-destructive profile; the description adds the behavior that actually matters: parsing is asynchronous, the call returns once the upload is stored rather than processed, and status must be polled. It also discloses auth requirements and free-of-credits cost, none of which is in 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?

Dense but every sentence carries load-bearing information — format restriction, async return semantics, polling target, auth role, tier limits, practical size guidance, and cost — with the core action front-loaded in the first clause.

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 write tool with no output schema and a fully covered input schema, the description supplies everything an agent needs to call it correctly: required role, accepted format, async semantics plus the follow-up tool to poll, and limits that affect whether to call it at all.

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 100%, so the schema already documents content, fileName, and projectId. The description's format constraint ('Only Apache/Nginx Combined Log Format text') and 'Pass the raw log text in content' largely restate or extend what the schema's parameter descriptions already say, so the baseline 3 applies.

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 ('Upload a server access log for background parsing') and names the feature family (Log File Analyzer / Bot Analytics), which cleanly separates it from log_analyzer_list_uploads, log_analyzer_daily_summary, and log_analyzer_top_paths.

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?

Explicitly covers when to use and when not: it directs the agent to poll log_analyzer_list_uploads for status, tells it to prefer the web UI for large logs, and states prerequisites (admin role, plan-tier caps on lines/upload and uploads/month). This is full when/when-not/alternative guidance.

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