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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only discovery operation but does not state whether there are side effects, authentication requirements, pagination, or rate limits. It also doesn't clarify what 'scored' means or how results are ordered. The lack of any behavioral context is a significant 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?

The description is a single, concise sentence that is front-loaded with the core action and outputs. It is not verbose and wastes no words, but it is under-specified rather than elegantly concise.

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?

The tool has only one parameter, no output schema, and no annotations, so the description must carry the full context. It does not explain what 'scored demand' entails, what the output format is, or any constraints on the 'limit' parameter. An agent would be under-informed about what to expect from the call, making it incomplete.

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 schema has one parameter 'limit' with a default but no description, and schema description coverage is 0%. The description does not mention the 'limit' parameter at all, so it provides no additional meaning beyond the bare schema. Since coverage is low, the description should compensate but fails to do so.

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 clearly states a specific verb ('Discover') and resource ('ME Demand Radar component'), and lists concrete outputs (scored demand, shortages, earning opportunities). It distinguishes the tool's purpose from the many siblings, though it doesn't explicitly differentiate from 'me_get_demand_opportunities' which could overlap.

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 on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or reference to sibling tools. An agent would have to infer usage from the tool name and context, which is insufficient given the large sibling list.

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