post_insight_resource_results

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

Beyond annotations (destructiveHint=true, not read-only), the description explains that existing unresolved results are removed and that server-computed fields are returned. This adds valuable context about the tool's behavior.

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 concise at three sentences with no filler. The first sentence effectively states the purpose. Slight improvement possible by adding bullet points for clarity.

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 complex tool with 5 parameters and no output schema, the description covers the core behavior (replacement, deletion) and mentions response details. Missing prerequisites or error conditions, but overall 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?

The description does not elaborate on individual parameters beyond what the input schema provides. With 40% schema coverage, the description could add more meaning, but it mentions the server-computed fields in the response, 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 description clearly states the tool replaces all resource results for an insight, using specific verbs like 'Replaces' and 'remove'. It distinguishes from similar tools like post_insight_result by describing bulk replacement, but does not explicitly name sibling 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 implies usage for bulk replacement and provides a specific case for deletion (empty array). However, no explicit when-to-use vs alternatives like post_insight_results or delete_insight_result is given.

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