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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the constraint that only public research is searched, which is a useful scope detail not present in annotations. However, it does not disclose any other behaviors like result limits, pagination, or authentication requirements, leaving the description to add minimal value beyond the annotations.

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, focused sentence that front-loads the action and purpose. There is no filler or redundant information; every word earns its place. It is appropriately concise for a simple search tool.

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?

The tool has a simple signature with one parameter and an output schema. The description states purpose and usage context, and annotations cover the safety profile. It does not explain the result format, but the output schema likely handles that. It is sufficient for an agent to invoke correctly, though it could mention limitations like the scope of 'research'.

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 provides 100% coverage for the single 'query' parameter, including a description that it is case-insensitive. The tool description adds no additional parameter details, so it does not enhance the schema's documentation. With high schema coverage, the baseline of 3 applies.

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 identifies the action ('search') and the target resource ('public Raintree Technology research'). However, it does not distinguish this tool from the sibling 'search_projects', which also searches but may cover a different scope. The purpose is clear but not uniquely differentiated.

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 explicitly states when to use the tool: 'when an agent needs to search public Raintree Technology research.' This provides a clear context, but it does not mention alternatives or exclusion cases, such as when to use 'search_projects' instead.

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