assets-get-data

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

No annotations provided, so description carries burden. It states 'includes all serializable fields and properties' which is behavioral, but does not explicitly confirm read-only nature or lack of side effects. Adequate but could be more explicit.

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 primary action, no extraneous words. Every sentence adds value: first states purpose, second provides usage guidance.

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 one parameter (well-described in schema) and no output schema, description explains what the tool returns (all serializable fields and properties). Could mention return data format, but sufficient for a straightforward getter with clear purpose.

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?

Input schema covers the single parameter with a detailed description of the three reference formats (basis). Description adds context about getting asset data but does not enhance parameter understanding beyond schema. Baseline 3 due to 100% 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?

Description explicitly states 'Get asset data from the asset file in the Unity project' with a specific verb and resource, and mentions it includes all serializable fields and properties. It also distinguishes from siblings by referencing 'assets-find' as a prerequisite.

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?

Clear when-to-use guidance: 'Use assets-find tool to find asset before using this tool.' This tells the agent the required preceding step and implies this tool is for fetching data after locating an asset.

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