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

With no annotations, the description carries the full burden. 'List' and 'public catalog' imply a safe, read-only operation with no auth barrier, which is useful, but it does not disclose whether the result is paginated, complete, or limited in any way.

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 front-loaded sentence with no filler. Every word contributes: verb, resource, audience, and scope.

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 public listing, the description covers scope and audience sufficiently. It omits explicit return-shape or pagination details, but no output schema exists and the simple nature of the call limits the risk.

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 zero parameters, so there is nothing meaningful for the description to add about parameters. Baseline of 4 applies because parameter semantics are not a concern for this tool.

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 states a specific verb ('List'), a clear resource ('AI agents a restaurant can hire on MyShop'), and the 'public catalog' scope, which immediately distinguishes it from search_agents or get_agent. An agent can tell exactly what this tool returns without opening the schema.

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 phrase 'public catalog' implies this is the unfiltered listing tool, but no explicit when-to-use guidance or alternatives are named. Sibling tools like search_agents exist for filtered lookup, yet the description does not point the agent to them.

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