get_serialized_fields

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

With no annotations, the description carries the full behavioral burden. It implies a read but never states that it is non-destructive, what happens if the type is not a MonoBehaviour/ScriptableObject, whether the assembly must already be loaded, or what form the fields come back in. For a query tool with zero annotation coverage this is a notable gap.

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 tight sentence with the core action and target-types front-loaded, and no filler. It is efficient, though there is very little content to be concise about.

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 low-complexity, two-required-parameter read tool with a fully documented schema and no output schema, the description is minimally sufficient. It still omits prerequisites and the nature of the returned field data, which an agent would need to use and chain the result correctly.

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% and both required parameters ('Assembly key', 'Full type name') are documented in the schema, so the baseline of 3 applies. The description adds only the target-type constraint (MonoBehaviour/ScriptableObject), not format or lookup rules for assembly/type_name beyond what the schema says.

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?

States a specific verb+resource ('Get all serialized fields') and restricts the target to MonoBehaviour or ScriptableObject, which separates it from generic siblings like inspect_type or decompile_type. It lacks explicit naming of which sibling to prefer when the agent wants broader type metadata, so it stops short of a 5.

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?

There is no when-to-use guidance, no prerequisites (e.g., whether the assembly must be loaded first), and no mention of alternatives such as list_monobehaviours, inspect_type, or decompile_type. The agent must infer that this is the narrow serialization-inspection path rather than the general type-inspection path.

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