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

The description provides important behavioral limits/traits like the 15-minute caching period. Since annotations already confirm it is read-only and idempotent, the description provides unique, valuable operational context.

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 perfectly front-loaded and highly efficient. It uses the HTTP method and path in the first part, followed by detailed scope and behavioral constraints, achieving maximum information density.

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 description covers the core functionality (what data), the scope (7 days/this month), the technical entry point (no key), and the operational constraints (15-minute cache), making it complete despite the lack of an output schema.

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?

Since there are zero parameters (schema coverage is 100%), the baseline is 3. The description adds minor value by indicating no key is needed, which relates to the input requirements even though the schema is empty.

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 explicitly states what is retrieved: 'verified members, leads listed in the last 7 days, prices posted and savings confirmed this month.' It uses a direct verb ('GET') and specifies the resource scope, clearly distinguishing it from other sibling tools which are generally prefixed 'commercebook_market'.

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?

The description notes that 'no key needed,' which is critical usage information that might differentiate this from other API calls that could require authentication, thereby guiding usage immediately.

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