ponzu_get_skill

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

No annotations are provided, but the description makes clear it is a read-only operation that fetches documentation and returns the full SKILL.md. It does not elaborate on potential side effects or rate limits, but for a simple fetch tool, the description is adequate.

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 very concise with two sentences, no wasted words. It gets directly to the purpose and provides a strong use recommendation.

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 no output schema, the description clearly states it returns the full SKILL.md with instructions for all contract interactions. This is complete for an onboarding/documentation tool. The context signals show no parameters and no output schema, but the description compensates fully.

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 no parameters, schema description coverage is 100%. The description adds no parameter-specific information, but none is needed. With 0 parameters, a baseline of 4 is appropriate.

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 fetches complete Ponzu skill documentation, returning the full SKILL.md. It distinguishes itself from sibling tools (which perform actions like deploying, swapping, farming) by being the documentation retrieval tool.

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 explicitly says 'Use this first to understand how Ponzu works', indicating it should be used as a prerequisite before other tools. This provides clear guidance on when to use this tool versus the action-oriented siblings.

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