websex_recommend_tools

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

No annotations are provided, so the description carries the full burden. It discloses only that matching is 'deterministic' (no LLM/randomness), but says nothing about return shape, whether it mutates anything, permission needs, or how 'objective' drives outcomes. Some signal ('deterministic') but far from adequate for a tool with zero annotation coverage.

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?

A single short sentence, front-loaded and waste-free. It is concise, though at the cost of substance rather than because it says a lot efficiently.

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?

An output schema exists, so return values needn't be explained. But with 0% param coverage, no annotations, and no usage routing, an agent cannot confidently form the 'objective' string or know the target_type enum. In a 150-tool namespace, this is under-specified.

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 0% and neither parameter is explained. 'objective' is the core control but its expected wording/granularity is unknown; 'target_type' defaults to 'web' but the allowed values are undefined. The description adds no parameter meaning beyond the schema, well below the baseline.

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 states a verb and resource ('Recommend WebSex tools') which is clear enough on its own, but it gives no hint of scope or domain relative to ~150 siblings. 'Deterministic objective matching' hints at the mechanism but not what recommendations look like or which tools could come back, so it barely distinguishes itself from catalog/engagement_plan siblings.

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, when-not-to-use, or named alternatives. Siblings like websex_catalog and websex_engagement_plan plausibly overlap with tool discovery/planning, yet the description never says when this is preferred. The agent must guess.

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