regenerate_project_memo

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

Discloses skipping behavior based on decision count and force parameter, warns about structured error without AI provider. No contradiction with annotations (readOnlyHint=true fits synthesis). Adds value beyond annotations.

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, front-loaded with purpose, no wasted words. Efficient and clear.

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?

Covers behavior, prerequisites, and output characteristics (length, LLM-written). No output schema, but description gives adequate context for agent to understand what to expect.

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 covers all 3 params with descriptions; description adds behavioral context (force ignores threshold, service_name scopes memo). Adds meaning beyond schema without being redundant.

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?

The description clearly states the tool synthesizes/refreshes a project memo of 250-400 words, distinguishing it from the sibling 'get_project_memo' by focusing on regeneration.

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?

Explains when to use (skip unless threshold met or force=true) and prerequisite (active AI provider). Missing explicit when-not-to-use or alternatives, but context is sufficient.

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