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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing: not whether the call is read-only, whether it consumes the appType/requestedFeatures as context, or what kind of output ('advisor' implies suggestions) results. No annotations plus no behavioral text is a total 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 short, but this is under-specification rather than conciseness — the single fragment is a namespaced title with a vague parenthetical and carries no actionable content 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?

For a 2-parameter recommendation tool embedded in a large sibling family, with no annotations and no output schema, the description provides none of the context needed to invoke it correctly or to distinguish its result from related recommend/map/plan tools.

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 two parameter descriptions are near-placeholders ('Application type.', 'Required feature.'). The tool description adds zero meaning on top of this, so the agent cannot infer valid values, the relationship between the two params, or whether either is required.

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 Flutter :: sdk.recommend (advisor)' effectively restates the tool name and namespace. The only semantic content is the parenthetical 'advisor', which hints at guidance but does not state a verb or what is actually recommended (SDK version, package, integration approach).

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 when-not-to-use, and no mention of the sibling alternatives that clearly overlap (flutter::ui.mode.recommend, flutter::feature.map, shared::sdk.recommend). An agent has no basis for choosing this tool over those.

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