rc_get_project_snapshot

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

No annotations provided, so description carries full burden. It describes the contents of the snapshot (apps, products, entitlements, customer sample) but does not disclose any potential side effects, authentication needs, or rate limits. Adequate for a read-only overview, but lacks extra behavioral context.

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?

Two sentences with no extraneous words. Front-loaded with the core purpose and a clear benefit statement.

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?

Completeness is high for a low-complexity tool with one optional parameter and no output schema. Explains the tool's composite nature and when to use it. Could mention the output structure or size limit of the customer sample, but not critical.

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?

Only one parameter (project_id) with full schema coverage. Description adds that if omitted, RC_DEFAULT_PROJECT_ID from env is used, which is valuable context beyond the 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?

Clearly states the tool provides a one-shot overview of a RevenueCat project including apps, products, entitlements, and a small customer sample. Distinguishes from sibling tools like rc_list_apps, rc_list_products, etc., which are granular list tools.

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 says it cuts 4+ tool calls down to 1 when you want the big picture, implying use when needing a high-level overview. Does not explicitly state when not to use, but context is clear from the contrast with sibling tools.

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