report_save

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

Discloses key behaviors: project isolation and automatic dashboard appearance. With no annotations, the description must cover safety and side effects; it omits whether the tool is idempotent or can overwrite existing reports.

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 concise sentences, front-loaded with purpose and key behavioral context. No wasted words.

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?

With an output schema present, return value details are not needed. Description covers purpose and storage behavior, but could mention constraints like size limits or update capability. Mostly complete.

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?

Input schema covers all 6 parameters with descriptions. The description adds no extra semantic meaning beyond the schema, so score is baseline 3 for high schema coverage.

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?

Description clearly states the tool saves a 'research/analysis report to the database', with a specific verb and resource. Among sibling tools like 'report_list' and 'report_read', this uniquely identifies the save operation.

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?

Provides context on when to use: reports are stored with project isolation, require no filesystem permissions, and automatically appear on the Dashboard. However, it does not explicitly exclude alternatives or state when not to use.

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