get_listing_quality

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states this is a read operation and explicitly declares that the local server is an introspection stub, not the actual hosted endpoint. This prevents misuse by agents expecting real data. However, it does not describe any potential side effects or output behavior.

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 two sentences with no superfluous words. It uses a clear bracket notation for domain/type and immediately states the purpose. Every sentence adds value without redundancy.

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?

Despite the schema covering parameters, the description is incomplete. It does not describe the return format, pagination, or what the stub actually returns. With no output schema, the agent needs to know what data to expect, but the description only vaguely mentions 'completeness scores and issues'. Given the tool's complexity (7 parameters, nested objects), this is insufficient.

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 input schema has 100% description coverage for all 7 parameters, so the schema itself provides full meaning. The description adds no parameter-specific information beyond what is already in the schema, so it doesn't elevate beyond the baseline of 3.

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 identifies the tool as a read operation for listing completeness scores and issues, using specific verb 'get' and resource 'listing quality'. The bracket notation '[Catalog / read]' reinforces the domain and action. It distinguishes from sibling tools by focusing on listing quality rather than performance or inventory.

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 lacks explicit guidance on when to use this tool versus siblings or alternatives. It mentions it's an introspection stub for a hosted endpoint, which informs that the local server is not functional, but does not provide context on what scenarios call for listing quality data or how it differs from other get tools.

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