getMapInfoByUserId

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

With no annotations, the description carries full disclosure burden. It does not mention read-only nature, permissions, rate limits, or any side effects. The name suggests 'ByUserId' but the parameter is mapId, creating ambiguity that is not addressed.

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, concise sentence that directly states the purpose without irrelevant filler. It is appropriately sized for the tool's simplicity.

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 no output schema and minimal annotations, the description is too terse to be fully complete. It does not describe the return values, what 'details' include, or clarify the mismatch between the tool name (ByUserId) and the actual parameter (mapId), leaving the agent under-informed.

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%, with mapId described as '地图ID'. The description repeats 'using map ID' without adding extra meaning about format, constraints, or behavior. This matches the baseline for full schema coverage.

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 states a clear verb+resource: '获取神岛平台地图详情' (get map details) with the method '使用地图ID' (using map ID). It distinguishes the action from sibling tools like list-oriented ones, though 'details' vs. 'release info' is not explicitly differentiated.

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. It simply states the function without mentioning prerequisites, exclusions, or scenarios where other map-related tools would be preferred.

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