tribal_staples

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. The description adds behavioral detail by specifying how results are grouped (lords/anthems, tribal synergy, best members, tribal support), which is beyond the annotations. No contradictions.

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?

Two concise sentences: first states the core purpose, second describes the grouping format. No fluff, efficient, and informative.

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 no output schema, the description should clarify what kind of data is returned (e.g., card names, counts, or ratings). It only says 'Best cards' and groups, but lacks explicit return structure. Adequate for a simple list but not fully complete.

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 is 100%, so parameters are well-documented. The description does not add parameter-specific details (e.g., format or color_identity usage) beyond what the schema provides. It mentions creature type and grouping, which are implicit from the tool's purpose, so minimal additional value.

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 it provides the best cards for a creature type with specific groupings (lords, synergy, members, support). The verb 'Best cards' and resource 'creature type' are clear. It implicitly distinguishes from sibling tools like 'edhrec_commander_staples' by focusing on creature types, but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives like 'color_identity_staples' or 'bulk_format_staples'. The description implies use for tribal staples, but no explicit when/when-not or alternative references.

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