treasure_pavilion

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

No annotations provided, so description bears full burden. Mentions summon modifies local vault but lacks detail on side effects (e.g., what is destroyed, authentication needs, rate limits). No mention of behavior beyond action descriptions.

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?

Well-structured with sections, emoji, examples. Front-loaded purpose and action types. Every sentence adds value, no fluff. Efficient despite length.

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?

Covers all actions, parameters, and search syntax. Output schema exists so return values not needed. Lacks error handling or edge cases, but sufficient for typical 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 coverage 0%, but description explains each parameter in detail: action with allowed values, query with search syntax, artifact_name with required conditions. Adds significant meaning beyond schema defaults.

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?

Description clearly states the tool is for searching, summoning, and exploring community artifacts. Uses specific verbs (search, summon, lineage) and resource (community artifacts). Distinguished from sibling tools like forge_agent or refine_agent.

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 describes action types and when to use each (search default, summon for pulling, lineage for exploring relationships). Provides search query syntax and examples. Does not explicitly mention alternatives or when not to use, but context is clear.

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