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

Beyond the annotations, the description discloses that entries go into a shared private backlog, that matching question/model/source scope merges, and that the action never grants priority, collection rights, spending, or publication. These are meaningful behavioral details for a mutation tool, though permissions and response behavior are not described.

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 short, front-loaded, and each sentence contributes useful information. Some sentences are telegraphic, which slightly reduces clarity, but there is little wasted text.

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 nested mutation tool with no output schema and 0% schema description coverage, the description covers purpose and safeguards but omits most parameter semantics and does not explain expected outcomes. It is not complete enough to fully guide correct invocation without additional schema interpretation.

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 input contains a nested object with multiple fields. The description clarifies research_route values and the merge key involving question/model/source scope, but it leaves title, why_useful, topic, source_urls, and idempotency_key largely unexplained.

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 and resource: "Add a focused question to the shared private research backlog." It is clear what the tool does, but it does not explicitly differentiate itself from nearby tools such as start_investigation or get_research_request.

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 first sentence implies this is for submitting research suggestions, but there is no explicit guidance on when to use it versus siblings or when not to use it. The mention of local_solo or curator_guided is a parameter instruction, not usage guidance.

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