get_user_posts

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

No annotations are provided, so the description carries the full burden. It only states the basic action 'Get a list' without mentioning pagination (though the schema has limit/cursor), authentication needs, sorting, or what data is returned. This is insufficient behavioral disclosure for a tool with no 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?

The description is a single, clear sentence with no waste. It is front-loaded with the main action and resource. It earns its place without unnecessary detail.

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?

The tool has 3 parameters, no output schema, and no annotations, yet the description only provides the core action. It omits important context like how pagination works (cursor/limit), what a post object contains, or any prerequisites. Given the absence of an output schema, the description should explain return behavior, but it does not.

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%, as each parameter (limit, cursor, username) has a description. The tool description adds no extra meaning about parameters, but the schema already documents them well. Baseline 3 applies because 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 description 'Get a list of posts by a Velog user' uses a specific verb and resource, clearly indicating the tool fetches a user's posts. It distinguishes from siblings like get_trending_posts (not user-specific) and search_posts (search across posts). The scope is explicit: posts by a specific Velog user.

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 implies usage when you need posts by a specific user, but it does not explicitly state when to use this tool versus alternatives or provide any 'when not' guidance. No sibling tools are referenced. The purpose gives context, but the guidance is only implied.

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