about_honestdogWhat HonestDog is, where its data comes from, and how to attribute it. Call this once before presenting HonestDog data. / Was HonestDog ist, woher die Daten stammen und wie sie zu zitieren sind.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true. The description adds behavioral context: it reveals platform identity, data sources, and citation requirements, which goes beyond the annotation.
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?
Bilingual description in two lines is concise and front-loaded with key information. Slightly redundant due to dual language, but overall efficient.
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 zero parameters, no output schema, and a simple informational purpose, the description covers everything an agent needs: what it is and when to call it.
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?
No parameters exist, so baseline is 4. The description compensates by explaining the tool's purpose and usage, adding value beyond the empty schema.
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?
Explicitly states what the tool provides: platform identity, data provenance, and attribution. Distinguishes from sibling tools that perform searches, making its unique purpose clear.
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?
States 'Call this once before presenting HonestDog data', giving explicit when-to-use guidance. No mention of when not to use, but the context implies it's a prerequisite setup tool, so alternatives are not needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: about, health profile, breeder search, breed search, and shelter dog search. No overlap.
All tools follow a consistent verb_noun pattern in snake_case: about_, get_, search_ (three times).
5 tools cover the essential functions of the HonestDog platform without unnecessary bloat or missing core capabilities.
The tool surface covers the main domains: breed info, health profiles, breeder directory, and shelter dogs. No obvious gaps.