macropulse

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

With no annotations provided, the description must fully disclose behavior. It mentions real-time data and payment requirements but omits important traits like rate limits, error handling, data freshness, or response format. The absence of these details limits the agent's ability to anticipate tool behavior.

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 description is well-structured with a clear opening and bulleted endpoints. It is somewhat verbose due to listing prices, but overall front-loads the essential payment requirement and purpose. Could be slightly trimmed without losing information.

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?

The tool has no output schema, so the description should explain return values. It only gives brief one-liners per endpoint without describing the output format, fields, or data structure. For a data-providing tool, this leaves significant uncertainty for the agent.

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 has 100% description coverage, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters; it merely repeats endpoint names with brief context. No extra semantics for lang, session, or event.

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?

The description clearly states the tool provides real-time macro intelligence for forex and CFD traders via listed endpoints. It distinguishes itself from sibling tools by specifying the target audience and endpoint types, though it lacks a single concise verb-resource statement.

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 includes a critical usage requirement (x402 payment via header) and endpoint names with prices, but does not provide guidance on when to use this tool versus alternative siblings. There is no explicit when-not or mention of scenarios.

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