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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds genuinely new traits: the call is free, it returns counts only, no content is returned, and the response includes match counts, newest date, and matched names. It stops short of auth or rate-limit detail, but the return-shape disclosure is the important gap-filler given no output schema.

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?

Three short sentences, front-loaded with the 'Free.' qualifier, then what it checks, then what it returns and what to use instead. No sentence is redundant and the negative constraint (no content) is stated exactly once.

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?

With no output schema, the description carries the return-value burden and does so explicitly (counts, newest date, matched names). Annotations cover the safety profile, so nothing an agent needs to decide or call this tool is missing.

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 100% and the single parameter is fully documented with examples and length bounds, so the schema does the heavy lifting. The description only restates 'a space company or topic' with no additional syntax or matching semantics beyond what the schema provides.

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?

States a specific verb and resource: check whether SNTL holds verified material on a company or topic. It explicitly contrasts itself with the content-retrieval sibling (submit_research_interest), so an agent can place it without opening a schema.

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?

Gives a clear trigger ('before asking a question') and routes the agent to the correct alternative for getting actual research. It does not address the other siblings (check_research_status, respond_to_research_offer), so exclusions are incomplete but the primary use context is unambiguous.

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