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

The description says the tool 'Replaces' the data room's existing sections and documents, which discards the prior arrangement, while the annotations declare destructiveHint=false. That mismatch can lead an agent to treat a wholesale overwrite as non-destructive; the description also omits permission requirements and whether removed document records are deleted.

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?

Three short sentences, front-loaded with the operation and followed by the routing guidance and the sharing clarification. Every sentence earns its place with no filler.

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 tool with an output schema, rich nested input schema, and annotations, the description covers the essential behavioral context: full replacement, approval prerequisite, and no sharing side effect. The remaining gap is the ambiguous destructive semantics and the role of memoArtifactId.

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 67% and the schema is rich and nested, so the baseline is 3. The description maps loosely to the 'sections' parameter but does not explain companyId, memoArtifactId, ordering behavior, or the per-call limits (20 sections / 200 items per section) that are only visible in 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?

The description uses a specific verb and resource ('Replaces the data room's sections and their documents') and clarifies the full-replacement semantics with 'in one call.' This distinguishes it from read-oriented siblings like fundraising_get_data_room and access-oriented siblings like fundraising_grant_data_room_access.

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?

It explicitly names the preferred alternative (fundraising_propose_change) and the precise condition for calling this tool directly: only after the founder has approved it. That is exactly the when-to-use/when-not guidance an agent needs.

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