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

There are no annotations describing side effects, persistence, or output behavior. The description says 'Record' but does not disclose whether the record is saved, transmitted, or acknowledged, nor whether the tool returns any confirmation or result. Since annotations are absent, the description carries the full burden of behavioral transparency, and it falls short.

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 conveys the tool's purpose, the condition for use, and the required input fields. It wastes no words and is 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?

Given that the tool has no output schema and a simple three-parameter input, the description covers what the tool does, when to use it, and what to include. It does not explain post-submission behavior or return values, but those are not strictly necessary for an agent to invoke the tool correctly in a gap-reporting context. The description is sufficiently complete for the tool's simple nature.

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 schema has full coverage, and each parameter description adds useful context beyond the parameter name. 'description' is clarified as 'the unmet need', 'example_query' is framed as an optional user query or scenario, and 'triggered_by_tool' is explained as the tool or scenario that exposed the gap. This gives an agent enough semantic understanding to populate the fields correctly.

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's purpose: to record an unmet analysis need. It specifies the resource ('unmet analysis need'), the intended trigger ('when existing tools cannot satisfy the request'), and the required content ('missing capability and an example query'). This is a precise and unambiguous statement of what the tool does.

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 usage guidance by stating that the tool should be used when existing tools cannot satisfy the request. It also instructs the user to include the missing capability and an example query. It does not explicitly name alternative tools or contrast with them, but the condition is clear enough for an agent to decide when this tool is appropriate.

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