Get platform stats

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

States 'Read-only, no input required, backed by GET /stats', disclosing safety and backend. With no annotations, this covers the main behavioral concerns, though data freshness is not explicitly addressed.

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?

Three sentences, each providing essential info: what it does, when to use, and behavioral note. No fluff, optimally front-loaded.

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?

Fully adequate for a zero-parameter tool with no output schema. Covers purpose, usage context, and behavioral traits.

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?

Zero parameters; baseline 4. Description adds value by listing the specific stats returned, which is beyond the empty schema.

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 states specific verb 'Get' and resource 'platform-wide stats', listing exact metrics (total raised, active project count, etc.). Clearly distinguishes from sibling tools which focus on individual projects or transactions.

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 recommends use for 'quick pulse check on the platform, e.g. before deciding whether to launch a new campaign'. Lacks explicit alternatives, but sibling differentiation is inherent.

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