Get Skin Weights

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

Annotations already declare readOnly Hint, idempotentHint, and destructiveHint false. The description adds value by explaining the default limit rationale (dense data) and pagination usage, without contradicting any 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?

Two sentences, front-loaded with purpose. Every sentence provides necessary context (function, pagination, default reason). 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?

For a simple read-only tool with annotations and output schema present, the description covers the main behavioral aspects (dense data, pagination). It doesn't detail error handling or return format, but these are likely covered by output schema and annotations. Good enough for effective use.

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 coverage is 100%, so the description doesn't need to add much. It adds context for the default limit and offset purpose, but the skin_cluster parameter lacks additional description beyond what's in the schema. Baseline 3 is appropriate.

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?

Clearly states 'Get per-vertex skin weights with offset/limit pagination', specifying verb (get), resource (per-vertex skin weights), and distinguishing pagination feature. Context with sibling 'skin.weights.set' reinforces the read purpose.

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?

Provides clear context: default limit 100 due to dense data, and recommends using offset for pagination on large meshes. Doesn't explicitly contrast with sibling tools, but the usage advice is practical and directly guides agent behavior.

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