Import Chat Room Message

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is largely covered. The description adds the confirm=true requirement, which is useful behavioral context beyond the annotations, but it does not explain what community state is changed, what side effects occur, or whether the operation is reversible. With annotations carrying most of the burden, this is a minimal but non-contradictory addition.

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 short and front-loaded, but the first sentence is a pure restatement of the title and does not earn its place. The second sentence is useful but minimal. It is concise, though not maximally structured because it wastes one sentence on tautology and omits key operational details.

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 destructive, open-world mutation tool with nine parameters, a nested payload object, no output schema, and no required fields, the description is far too thin. It does not explain the import source, return behavior, permissions, idempotency semantics beyond annotations, or how to choose it over sibling message-creation tools. Annotations and schema cover safety and parameters respectively, but the description leaves major operational gaps.

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%, meaning every parameter including the nested payload object is fully documented in the input schema. The description only mentions confirm=true, which is already explained in the schema, and adds no syntax, format, or structural detail beyond what the schema provides. Per the rubric, a baseline of 3 is appropriate when the schema does the heavy lifting.

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 first sentence merely restates the tool title/name, so it adds no purpose information beyond structured fields. The second sentence says the tool 'Changes community state' but does not clarify what 'import' means, where the message comes from, or how it differs from siblings like send_message or create_comment. The verb+resource are technically present, but the description remains vague about the actual operation.

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?

The only usage-like guidance is that confirm=true is required 'for the user-requested action,' which is a parameter-setting rule rather than a when-to-use statement. There is no guidance on when to choose this tool over alternatives such as send_message, create_comment, or other chat/message tools in the sibling list. No prerequisites or exclusions are provided.

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