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. '(advisor)' weakly implies a non-mutating, recommendation-style response, but there is no disclosure of what inputs are required, what form the recommendation takes, or whether any state is affected. For a zero-annotation tool this is a substantial 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?

It is a single short fragment with no wasted words, but conciseness is only valuable when content exists; here the brevity reflects under-specification rather than tight writing. Nothing is front-loaded because there is nothing to front-load.

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?

With no annotations, no output schema, and a 2-parameter input that is only half documented, the description leaves the agent unable to predict the tool's behavior or result. It is not remotely complete for a tool in a 100+ sibling namespace.

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?

With only 50% schema description coverage, the description must compensate for undocumented parameters, and it adds nothing: neither 'appType' nor 'requestedFeatures' is clarified beyond what the schema already states. No syntax, cardinality, or example values are supplied.

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 is essentially the namespaced tool name restated ('sdk.recommend') plus the bare qualifier '(advisor)'. It never says what gets recommended (SDK package? version? integration approach?) or how it differs from the many sibling recommend/map tools such as ui.mode.recommend or feature.map. This is closer to a tautology than a statement of 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?

No when-to-use guidance, no prerequisites, and no named alternatives. The single word 'advisor' hints at an advisory role but gives the agent no condition under which to select this tool over sdk.recommend on other platforms or over ui.mode.recommend.

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