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

No annotations exist, and the description does not disclose behavioral traits such as read-only behavior, error handling, permissions, or side effects. It mentions only the content of the returned entry, not how the operation behaves.

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 very short and avoids fluff, but it is a fragment, not a sentence, and omits enough context that brevity crosses into under-specification. It is front-loaded with the domain name, but a more complete phrase would improve structure.

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 tool with no annotations and no output schema, the description should provide more than a hint about return contents. It does not say what AWARE is, where an ID comes from, or what 'notes and cross-links' mean, leaving an agent to rely on the name and schema.

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?

With 0% schema description coverage, the description had to explain the meaning of the 'id' parameter but does not mention it at all. 'One entry' loosely connects the ID to a single AWARE record, but no detail is given about ID format, source, or how it relates to sibling tools.

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 identifies the result as a single AWARE entry with notes and cross-links, which signals a singular retrieval, but it is a noun phrase rather than an explicit statement of what the tool does (e.g., 'Returns' or 'Gets'). It does not directly explain the action, though the tool name 'aware_get' and 'one entry' help infer it.

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?

No information is provided about when to use this tool versus aware_search or any other sibling. The phrase 'one entry' loosely implies looking up a single record, but there is no explicit condition, such as 'use when you have an ID' or 'use search when you do not have an ID.'

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