PetSmart MCP Server

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

No annotations are provided, so the description carries the full burden. It mentions booking a class but doesn't disclose behavioral traits such as whether this is a read-only or mutating operation, authentication requirements, rate limits, confirmation processes, or what happens after booking (e.g., email confirmation). For a booking tool with zero annotation coverage, this 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 appropriately sized with two sentences: one stating the purpose and one listing class types. It's front-loaded with the core function, and each sentence adds value without waste. However, it could be slightly more structured by explicitly separating purpose from details.

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?

Given the complexity (booking tool with 7 parameters, no annotations, no output schema), the description is incomplete. It covers the purpose and class types but lacks behavioral context (e.g., mutation effects, response format) and doesn't leverage sibling tools for guidance. It's adequate as a minimum but has clear gaps for effective agent use.

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?

Schema description coverage is 100%, so the schema already documents all 7 parameters with clear descriptions. The description adds minimal value beyond the schema by listing example class types, but it doesn't provide additional syntax, format details, or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the tool's purpose: 'Book a dog training class at PetSmart.' It specifies the verb ('Book') and resource ('dog training class'), and distinguishes it from siblings like 'schedule_grooming' by focusing on training. However, it doesn't explicitly differentiate from other booking tools (none listed), so it's not a perfect 5.

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 implies usage by listing class types ('puppy training, beginner obedience, advanced training, and specialty workshops'), suggesting when to use it based on training needs. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'schedule_grooming' or prerequisites (e.g., dog age requirements), leaving some ambiguity.

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