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

There are no annotations, so the description must carry the full behavioral load. It does disclose what the response contains (payment mode, fee policy, identity requirements, verticals, endpoint map), which is genuinely useful return-value context given there is no output schema. However, it never states that this is a read-only lookup with no side effects, and says nothing about authentication or rate limits - gaps that matter 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?

Two short sentences, front-loaded with the identity of the resource and followed by the directive to call it first. Nothing is redundant; the enumerated fields earn their place by telling the agent what information it will receive.

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 zero-parameter discovery tool with no output schema and no annotations, the description covers what the tool is, what it returns, and when to call it. The remaining omission is that it does not explicitly frame the call as a safe, non-mutating read, which is the one piece of behavior an agent would want reassurance on.

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?

With zero parameters, the baseline is 4, and the description appropriately provides no parameter discussion. It does not waste words re-describing an empty schema, and the enumerated response contents indirectly reassure the caller that no input is needed.

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 names a specific resource (the EverList hub manifest) and enumerates its contents - payment mode, fee policy, identity requirements, verticals, endpoint map. That is concrete enough to distinguish it from siblings like everlist_search or everlist_verticals, which are clearly operational rather than informational. It stops short of a crisp verb+scope sentence, but 'Discovery' plus the enumerated manifest payload carries the meaning.

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?

'Call this first' is an explicit ordering directive that tells the agent when to invoke it relative to everything else. What is missing is a when-not clause or a named alternative for agents that already have the manifest in context, but the sequencing guidance is strong and unambiguous as far as it goes.

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