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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds one genuinely new behavioral fact beyond that: fixed rules may flag legal, security, compliance, or cost risks. It does not say whether flags block creation or merely annotate the result, nor what the call returns, so the added context is real but thin.

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 no filler. The core action is front-loaded and the secondary risk-flagging behavior follows, so nothing is wasted.

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 simple three-parameter create tool with a complete schema and annotations covering the safety profile, the description is close to sufficient. However, there is no output schema, and the mention of risk flags implies a return payload whose shape and effect on the caller remain unexplained.

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 description coverage is 100%, so all three parameters (venture, title, notes) are already documented in the schema with constraints. The description adds no syntax, format, or naming guidance beyond that, so the baseline 3 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?

The description gives a specific verb and resource: 'Adds a new idea card to a venture's mind map in Flowmaps.' The resource (idea card / mind map) is clearly distinct from every sibling, which deals with features, ventures, projects, or build instructions. It stops short of an explicit sibling comparison, so a 4 rather than a 5.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as start_feature or import_project. The agent must infer from the name alone that this is the tool for capturing a raw idea rather than creating a structured feature.

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