getModelListByUserId

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'get list' with no mention of side effects, required permissions, pagination behavior, rate limits, or response format. The tool name implies a read-only operation, but this is not explicitly stated in the description.

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, front-loaded with the action and resource. It contains no redundant information and is appropriately sized for a simple list operation.

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?

Despite being a simple tool, the description lacks return value information, definition of what constitutes a 'model', and any behavioral context. With no output schema and no annotations, the description is too minimal to fully inform an agent about the tool's complete behavior.

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 input schema already provides descriptions for all three parameters (limit, offset, userId) with 100% coverage. The tool description adds no extra meaning beyond restating that it uses the user ID, so it meets the baseline for schema-covered parameters without adding value.

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 '使用用户ID获取神岛平台模型列表' (Get the list of models on the Shendao platform using user ID) clearly identifies the action (获取) and the resource (模型列表). It distinguishes from sibling tools like getMapListByUserId by specifying '模型' (models) rather than maps, making the purpose unambiguous.

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 no guidance on when to use this tool versus alternatives. It merely states its function without contextual cues about scenarios, prerequisites, or exclusions. The sibling list contains similar tools, but the description doesn't clarify when this one is preferred, leaving the agent to infer usage.

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