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

Goes well beyond the readOnlyHint annotation: discloses the 12h exclusive-match window before a deal opens to all scouts, the exact error codes (403 not_a_scout / scout_not_approved) and the corrective action with the signup URL, and confirms the tool is free. This is unusually rich behavioral context for a read tool.

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?

Front-loaded with audience and payload, then trigger, then behavioral caveats, then failure handling. Every sentence carries distinct information; nothing is repeated from the schema or annotations except the harmless 'read-only' confirmation.

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?

With no output schema, the description carries the full burden of describing return values and does so item by item (post, why it fits, drafted opener, status, links). Audience gating and error recovery are also covered, so an agent can call and handle this tool without further information.

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?

The tool takes no parameters, so there is nothing to disambiguate; the description instead enumerates what each returned deal contains, which is the useful semantic detail here. Baseline 4 applies for a zero-parameter tool.

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?

States a specific verb and resource ('get scout deals') plus the exact payload: today's founder post picks with post, fit rationale, drafted opener, status and links. This is clearly distinguishable from siblings like find_open_campaigns or get_my_submissions.

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?

Gives an explicit trigger ('Use it when the user asks what deals do you have for me?') and prescribes the response behavior (show each deal briefly, let the user pick). It does not name the natural follow-on tools such as claim_deal or release_deal, so the user is left to infer the next step.

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