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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not whether the tool is read-only, what it returns, whether it depends on prior state, or any constraints. "(advisor)" is too vague to convey behavior.

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, but that shortness is under-specification rather than conciseness — the single fragmented line carries no load-bearing content. There is nothing to front-load because no substantive statement is made.

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?

A 2-parameter tool with no annotations and no output schema needs the description to explain purpose, behavior, and return expectations. This one provides none of that, leaving an agent with no basis to call it correctly among ~14 sibling tools per platform.

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 only 50% and the description adds no parameter meaning whatsoever — it never mentions appType or requestedFeatures. The schema's own "Application type." and "Required feature." strings are terse and the description does nothing to compensate for that gap.

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 a restatement of the tool name plus namespace ("mediasfu-shared :: sdk.recommend"), with "advisor" as the only additional word. It hints at recommending an SDK but doesn't say what is being recommended, for what input, or what the agent gets back. Against dozens of sibling sdk.recommend variants across platforms, it offers no differentiation beyond the namespace prefix.

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, when-not-to-use, or alternative guidance at all. The crowded sibling list (feature.map, integration.plan, ui.mode.recommend, etc.) makes routing guidance essential, and none is provided.

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