import_my_naver_blog

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

Annotations mark this as a write with openWorldHint=true, and the description adds real value beyond that: only public posts are imported, and critically it warns that the service cannot verify ownership, so misuse is the user's responsibility. It does not cover rate limits, failure modes, or what happens to duplicate posts, but the ownership caveat is substantive.

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?

Two sentences, front-loaded with the action, followed by the ownership constraint. No filler or restatement of the tool 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?

An output schema exists, so return values need no explanation, and the schema covers all parameters. The description supplies the key behavioral caveat (ownership unverifiable, public posts only). Missing only auth/prerequisite context, which is minor given the annotation profile.

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% and all three parameters (blog, count, style) are already documented in the schema, including the note about style vs kind. The description adds no parameter-level detail, so 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 — fetching and inserting recent public posts from the user's own Naver blog — which is distinguishable from siblings like add_my_writing (manual entry) and read_my_writing (retrieval). It does not name a sibling explicitly, but the scope is concrete enough for selection.

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 description gives one explicit exclusion — only the user's own blog, never someone else's — which is genuine usage guidance. However it says nothing about when to prefer this over add_my_writing or what prerequisites (e.g. being logged in, blog reachability) are needed.

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