get_render_pipeline_migration_hints

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

With no annotations supplied, the description carries the full behavioral burden. It implies a non-mutating analysis ('Infer... flag'), but never says whether it only reads project state, how the risk is graded, whether results are cached, or what happens on older Unity versions despite the '6.5+' qualifier.

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 front-loaded sentence that puts the action and the risk flag first, with the version constraint trailing as a qualifier. It is efficient, though the compressed acronyms (BIRP, RP) make it slightly less self-explanatory than it could be at the same length.

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 zero-parameter read tool with no output schema and no annotations, the description covers the essential purpose but not the return shape — what a 'risk flag' looks like, which pipelines are reported, or what evidence backs the inference. It is adequate to select the tool but thin for interpreting results.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description contradicts or misrepresents the empty input schema.

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 names a specific action (infer the render pipeline as BIRP vs URP/HDRP) and a specific output (flag Built-in RP deprecation / migration risk), which clearly separates it from siblings such as list_render_pipelines or list_render_textures. It loses a point only because the abbreviation BIRP is unexplained and the relationship to the other render tools is left implicit.

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 states what the tool does but never states when to use it, when not to, or how it relates to alternatives like get_feature_set_inference or get_platform_build_hints. The '(Unity 6.5+)' qualifier hints at a scope condition but is not turned into usable guidance.

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