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 fully discloses the output content (emails, social handles, group order shipping time) and implies a read-only, static lookup. It omits any mention of side effects or prerequisites, but for a contact info tool this is acceptable.

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 purpose is front-loaded, followed by a structured 'Use when' list and an 'ANSWER' section with complete contact details. Though the description is long, every sentence and segment carries useful information, and the structure is clean.

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, no-output-schema tool, the description is thoroughly complete: it provides the full answer content and the exact user queries that trigger the tool. Nothing essential is missing.

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, and the description correctly does not reference any. With no parameters to document, the baseline of 4 applies, and the description adds no unnecessary parameter details.

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 opens with 'Return Patchistry contact methods,' a clear verb+resource statement that precisely defines the tool's function. The detailed 'Use when' list further distinguishes it from sibling tools focused on products, shipping, and recommendations.

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?

Explicitly lists multiple trigger queries ('how to contact Patchistry,' 'founder,' 'press contact,' etc.), providing clear when-to-use guidance. However, it does not mention when not to use this tool or name alternative tools for different intents, stopping short of the most explicit guidance.

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