Update Basecamp Document

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

Annotations (readOnlyHint=false, destructiveHint=false) are not contradicted. The description adds behavioral context by detailing HTML rules and partial operation options, which go beyond the annotation's simple flags.

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?

The description is well-structured: first the purpose and token-saving advice, then HTML rules in a bulleted list. It is slightly long but each sentence adds value. Front-loading the token-saving tip is good.

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?

The description covers parameters and usage well, but does not mention what is returned (e.g., the updated document). With no output schema, a brief note on return value would improve completeness. Otherwise, it is adequate.

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 coverage is 100%, but the description adds significant value by explaining the interplay between content and partial operations (their mutual exclusivity) and providing HTML formatting guidance, which is not 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 title and description clearly indicate it updates a document ('Update a document'), distinguishing it from create or read tools. However, it does not explicitly differentiate from other update tools like basecamp_update_message, but the verb+resource is clear enough.

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 description advises using partial content operations (append/prepend/search_replace) to save tokens, which is helpful. It does not explicitly state when to use this tool vs. create or other update tools, but the context of updating is implied.

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