pillar_direct_dca_invite

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

With no annotations, the description carries full burden and does supply real domain behavior: the invite creates a mutual weekly-boost commitment. However it omits mechanics that matter for a mutation call — whether the partner must accept, whether an invite can be duplicated, and any auth/precondition requirements.

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 core action and its consequence are front-loaded in two tight sentences with zero padding. The closing tip is somewhat tangential but is clearly demarcated and short.

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?

Adequate for a one-parameter mutation with a fully documented schema, and the streak/accountability context is genuinely useful. Still short of complete for an unannotated write tool: invite lifecycle (pending/accepted), failure modes, and required wallet state are all unstated.

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% and the single parameter already documents email-or-Stacks-address with the SP... format. The description's 'by email or wallet address' merely restates it, adding no format, validation, or resolution detail, so baseline 3 applies.

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?

States a specific verb and resource (invite a DCA partner) with the two accepted identifier forms. It is clear on its own, but it never distinguishes itself from the very similarly named sibling `pillar_dca_invite`, which an agent choosing between the two would need.

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 implies the scenario (pairing with an accountability partner who must boost weekly), but gives no explicit when-to-use or when-not-to-use guidance and names no alternative. The `earning_opportunities` tip is adjacent context rather than a routing instruction.

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