social_media_posting_start_csv_finalize

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

The description does not disclose any behavioral traits beyond the annotations. It does not state whether the operation is asynchronous, what side effects occur, or what the response looks like. Even though annotations indicate a mutating action (readOnlyHint=false), the description adds no context about what 'finalize' actually does, leaving the agent with no behavioral expectations.

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 brief, but this is under-specification rather than thoughtful conciseness. It lacks structure and does not front-load any useful information. It is a single clause that adds no value beyond the name.

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 tool with 3 parameters and no output schema, the description is entirely inadequate. It fails to explain what 'finalize' means in the context of CSV posting, what the CSV id refers to, or how this fits into the overall social media posting workflow. An agent has no clue when to invoke this tool or what to expect.

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 schema description coverage is 100%, so each parameter (id, userId, locationId) already has a description. The tool description does not add any additional meaning or context to the parameters, but the baseline is 3 because the schema covers them adequately.

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 'Start CSV Finalize' is essentially the tool name rephrased. It does not state what 'finalize' means, what resource it acts on, or what the outcome is. It is a tautology that provides no distinguishing information from the many sibling social_media_posting_* tools.

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 on when to use this tool versus alternatives like social_media_posting_delete_csv or social_media_posting_get_csv_post. There is no mention of prerequisites, workflow context, or conditions that would trigger this tool.

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