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

The annotations already mark readOnlyHint false and destructiveHint true, so the agent knows this is mutating, but the description adds no context about what the destructive behavior is or what side effects occur. The only behavioral clue is the 'dry_run' argument name, but the description never explains that dry_run might prevent actual 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 very short, but this is under-specification rather than valuable conciseness. 'Args: dry_run' looks like a placeholder and does not provide meaningful content that helps an agent call the tool correctly.

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 destructive annotation, the massive sibling tool list, and zero parameter schema coverage, the description is severely incomplete. Missing critical information includes how the CSV is supplied, what dry_run actually controls, which post fields are expected, and whether bulk upload is additive or can replace/delete existing posts.

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 0%, and the description merely repeats the parameter name 'dry_run' without explaining what it controls or how it should be used. A parameter named dry_run is far from self-explanatory, and the description must 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, 'Bulk upload from CSV', exactly matches the tool's title and name, so it is almost a pure tautology rather than a substantive explanation. It identifies a verb and resource, but an agent gets no detail about whether this creates new posts, replaces existing ones, or imports into a queue.

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 given about when to use bulk upload versus sibling tools like posts_create or posts_cross_post. The description does not state prerequisites, scenarios, or exclusions, so the agent cannot decide between this tool and alternatives based on the description alone.

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