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

With no annotations, the description carries the full burden of behavioral disclosure. It adds a privacy constraint but does not disclose side effects, persistence, visibility, ownership, mutation behavior, or failure/return behavior. 'Contribute' implies a write action, but the operational consequences are left unspecified.

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 two short sentences with no filler. The main action is front-loaded, and the privacy constraint is a single additional sentence. It is efficient and easy to parse.

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 six parameters, three required, no annotation coverage, no parameter descriptions, and no output schema, this description is far too sparse. An agent cannot reliably construct a valid request, interpret the required fields, or know what happens after submission.

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 0% and the description names none of the six parameters. Required fields like subject, problem, and finding, as well as optional evidence, confidence, and environment, are completely undefined in terms of expected content or format. The description adds no parameter-level meaning.

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 + resource ('Contribute a compact reusable finding') and the tool name reinforces the action. It is clear that this is for adding a finding, but it does not explicitly distinguish itself from the sibling submit_question or explain what qualifies as a 'finding'.

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?

There is a clear caution about not submitting secrets or private data, but no guidance on when to use this tool versus alternatives like submit_question or search_findings. The description implies a finding-contribution context but never states conditions or exclusions beyond the privacy warning.

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