hub_card_set

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

Discloses that hand-written frontmatter and Facts are preserved. No annotations provided, so description carries behavioral burden adequately.

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 sentences: first states purpose and differentiation, second gives use case and notable behavior. No waste.

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?

Does not explain return value, but inputs and behavior are well-covered. Adequate for the tool's complexity and given no output schema.

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 covers 100% of parameters. Description adds meaning for 'digest' (3-6 lines) and 'project' (name/slug). 'by' is minimally explained but schema covers it.

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?

Clearly states 'Create or update a project card' with specific inputs (name and digest). Distinguishes from sibling hub_sync by noting no folder needed.

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 says when to use: 'capture a project that is not a local git checkout, e.g. when harvesting a dialog.' Mentions hub_sync as alternative.

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