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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, whether it needs prior context (features already mapped, env preflight done), whether results are deterministic, or what shape the advice takes. Zero behavioral context for a tool with an array parameter and no output schema.

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?

It is short and front-loaded with the qualified name, and the alias list has marginal routing value for matching user phrasing. But the compactness comes from omission rather than discipline — it spends its only sentence on metadata instead of purpose.

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 two-parameter advisor tool with no annotations, no output schema, and half-documented parameters, the description should at minimum anchor the tool in the workflow and describe the return. It does neither, leaving an agent unable to distinguish it from unity::integration.plan or unity::ui.mode.recommend.

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 description coverage is only 50% ('Application type.' and 'Required feature.' are near-useless stubs), and the description compensates with nothing — no valid values for appType, no semantics for requestedFeatures ordering or mutual exclusivity, no hint about how maxItems: 32 maps to real feature vocabularies.

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 text is essentially the tool name restated with a platform prefix and an '(advisor)' tag, plus routing aliases. 'recommend' hints at a recommendation function but never states what it recommends — SDK choice, configuration, features — or against what criteria. It is closer to a tautology than a statement of purpose, though 'advisor' adds a sliver of meaning.

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 at all, despite dozens of plausible adjacent siblings (unity::integration.plan, unity::feature.map, unity::api.reference.search, and every other language's sdk.recommend). Nothing tells an agent whether this tool is the entry point, a final step, or scoped by appType.

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