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, yet it discloses nothing about determinism, whether recommendations are advisory only versus actionable, whether it reads project state, or what it returns. A single label '(advisor)' is the only hint and it is unexplained.

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 line with no padding, but brevity here reflects under-specification rather than conciseness. There is no front-loaded purpose statement an agent can act on.

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, no required params, and only half the parameters documented, the description would need to explain what a recommendation call does and returns. It supplies none of that, leaving an agent unable to call or interpret this tool 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 description coverage is only 50% (appType is glossed merely as 'Application type.' and requestedFeatures items as 'Required feature.'), and the description adds no meaning about accepted values, format, or how these inputs shape the recommendation. It neither compensates for the coverage gap nor exploits the little schema text available.

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 'MediaSFU ReactJS :: sdk.recommend (advisor)' only restates the tool name and namespace with an added parenthetical '(advisor)'. It never says what is being recommended (SDK packages? integration approach? version?) or the recommended output, so it is close to a tautology rather than a specific verb+resource statement.

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 routing guidance. Siblings like integration.plan, feature.map, ui.mode.recommend and the shared::sdk.recommend variant all plausibly overlap, and the description gives no basis for choosing among them.

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