get_campaign

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

No annotations provided, so description must fully disclose behavior. It says 'Get full details', which suggests a read-only operation, but does not explicitly confirm non-destructive nature, authentication needs, or rate limits. The description is minimal but not contradictory.

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 a single, focused sentence with no fluff. Every word contributes to purpose clarity. Ideal length for a simple tool.

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?

Given low parameter count and no output schema, description provides the core purpose but lacks details on what 'full details' entails (e.g., fields returned, pagination, or error cases). Adequate for a straightforward getter but incomplete for full agent understanding.

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 0%, meaning description adds no explanation of parameters. While 'campaignId' is intuitive as an ID, the description does not elaborate on its format, source, or constraints, leaving the agent to rely solely on the schema's type and required status.

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 verb 'Get' and resource 'campaign', specifying it returns 'full details of a specific Clawsfund campaign'. It effectively distinguishes from siblings like 'fund_campaign' (funding), 'list_campaigns' (listing), and 'search_campaigns' (searching).

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 implies usage when needing detailed info on a single campaign but provides no explicit guidance on when to use this over siblings (e.g., vs list_campaigns for overview or search_campaigns for filtering). No when-not or alternatives mentioned.

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