getMapCommentListByUserId

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'get list' without mentioning authentication, pagination behavior, rate limits, or return format. The read-only nature is implied by the name but not elaborated, offering minimal additional context.

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?

A single concise sentence that clearly states the primary function without redundancy. The structure is efficient and front-loaded, with no unnecessary words.

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 5 required parameters and no output schema, the one-sentence description is insufficient. It fails to explain the relationship between contentId and contentType, note that all parameters are required, or provide any context about the response format or usage conditions. The name/description ambiguity further reduces completeness.

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 descriptions cover all 5 parameters with useful details like max limit and orderBy codes, meeting the baseline. The description adds little beyond restating the use of map ID, so it provides marginal value over the schema.

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 clearly states it retrieves a list of map comments using the map ID, which is a specific verb and resource. It distinguishes from generic comment tools like getCommentList, but the tool name mentions 'ByUserId' while the description focuses on map ID, creating slight ambiguity about the intended scoping.

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 provided on when to use this tool versus alternatives such as getCommentList or getMapListByUserId. The description only states what the tool does without explaining the appropriate use case, prerequisites, or exclusions.

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