about

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

With no annotations provided, the description carries the full burden of disclosing behavior. 'What is known' suggests a read-only retrieval operation, which is useful, but it does not state what happens for unknown entities, whether any side effects occur, or whether special permissions/identifiers are needed.

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 clear sentence with no filler, and the core semantic ('what is known about one thing') is front-loaded. It earns its place without redundant phrasing.

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 single-parameter tool with an output schema present, the description is minimally adequate: it names the input concept and implies retrieval. But it leaves the parameter format ambiguous and gives no routing guidance relative to 'search' and 'remember', which are the main completeness gaps.

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 input schema provides only a required property named 'thing' with no description, so schema coverage is 0%. The description partially compensates by defining the parameter as a file, person, or topic, but it does not specify the expected format, identifier type, or how to distinguish between those referent kinds.

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 conveys a lookup-style tool for a single referent ('What is known about one thing') and gives concrete examples ('a file, a person, a topic') that clarify the resource scope. It is distinguishable from the siblings 'search' and 'remember' by emphasizing facts about one entity rather than discovering or storing, though it does not name the siblings directly and uses the vague word 'thing'.

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?

Usage is implied: use this tool when you need known information about a single file, person, or topic. However, there is no explicit guidance about when to prefer 'search' for broader discovery or 'remember' for storing knowledge, and the siblings are not mentioned in the description.

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