Recurring Create Recurring Stream

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

Description minimally notes that data modification occurs, which aligns with annotations (non-readonly), but fails to disclose any specific traits like idempotency, error conditions, or side effects beyond the basic creation.

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?

Description is very short (two sentences), but the second sentence is vague and could be removed or clarified; no wasted words but also lacks substance.

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?

For a tool with 8 parameters (4 required) and no output schema, the description fails to explain the meaning of recurring streams, expected input formats, or return values, leaving the agent underinformed.

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?

Description adds no information about the 8 parameters; with only 25% schema coverage, the agent receives no help understanding merchant_id, frequency, amount, base_date, etc.

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 creates a recurring stream, but the phrase 'may create or update Monarch data' introduces ambiguity about the primary action, especially given the existence of a separate update 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?

Description provides no guidance on when to use this tool versus alternatives like update or remove, and lacks prerequisites or conditions.

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