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

No annotations exist, and the description only implies a read-only discovery action with 'Discover.' It does not disclose output shape, limit behavior, error conditions, or side effects.

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?

Single sentence, no redundant wording, and directly names the action and source.

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?

Given the simple one-parameter schema, the description covers the basic purpose, but omits necessary usage context and limit semantics. An agent would still need to infer when to call it and what the default/limit means.

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?

The only parameter, limit, is not described at all; the schema only supplies type and default. The description adds no meaning to limit, leaving agents to guess its effect.

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 identifies a specific action ('Discover') and resource ('capability demand and shortage opportunities') sourced from 'ME Demand Intelligence.' It conveys the tool's purpose but does not explicitly distinguish it from related sibling tools like me_demand_radar or me_discover.

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 guidance is provided about when to use this tool versus alternatives such as me_demand_radar, me_discover, or me_find_*. It lacks any conditions, exclusions, or examples.

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