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

No annotations are provided, so the description must carry the behavioral burden. It usefully discloses an auth prerequisite, that results are scoped to the caller's own private data, and that the window is 'recent' rather than complete history, but it says nothing about pagination, result limits, or whether the operation is strictly read-only.

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 short sentences with zero filler: the resource and scope are front-loaded, and the auth prerequisite is stated plainly afterward. Every clause earns its place.

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?

For a zero-parameter, non-destructive listing tool with no output schema and no annotations, the description names the two categories of items returned and the auth requirement. It leaves the exact return shape and any recency cutoff undefined, which is a modest gap but not a blocking one.

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 zero parameters, so there is nothing for the description to disambiguate; the empty schema is self-explanatory. Baseline of 4 applies.

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 ('List') and resource ('recurring work recipes and recent proposal cycles'), with scope narrowed by 'your private'. It does not name the closely-named sibling manage_recurring_work or explain the boundary between listing and managing.

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 only precondition offered is 'Requires API key', which is auth, not usage guidance. Nothing tells the agent when to call this versus manage_recurring_work, list_outcome_recipes, or list_work_opportunities, and no exclusions are stated.

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