basecamp_activate_recording

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Reactivate' indicates a mutation, but the description does not explain side effects, whether it restores associated items, permission requirements, or the return value. This is a significant gap for a write operation.

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 a single, concise sentence that immediately states the action and target. There is no redundancy or fluff, making it efficient and front-loaded.

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?

As a mutation tool with no annotations and no output schema, the description should provide more context about the operation's effects and any prerequisites. It does not mention what 'activate' entails, what happens if the recording isn't trashed/archived, or the response format, leaving the agent under-informed for a destructive-reversal action.

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 description adds no parameter semantics beyond the input schema. The schema already describes recording_id, while project_id remains self-explanatory but undocumented. With schema coverage at 50%, the description fails to compensate for the missing project_id context or offer any additional usage details.

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 the specific verb 'Reactivate' and identifies the resource as 'Basecamp recording', also scoping to 'trashed or archived' states. This clearly conveys the tool's purpose and inherently distinguishes it from sibling tools that trash or archive recordings, though it does not explicitly name those alternatives.

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 provides clear context by specifying the target state ('trashed or archived'), implying this tool is for undoing those operations. However, it does not explicitly state when not to use it or mention alternative tools, so it stops short of a 5.

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