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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Return' implies a read operation, but the description does not explicitly state that it is non-destructive, whether it requires any permissions, or what happens if no results are found. It only notes the source ('runtime log'), which is limited context.

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 states the core purpose without any fluff. It is front-loaded with the verb and object, making it easy to scan. No unnecessary words or repetition.

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 description lacks essential context for a tool with no output schema and minimal parameters. It does not explain what 'compact Director results' means, what the return format is, how the limit affects the output, or when this tool should be used relative to neo_director. These gaps could lead to incorrect invocation.

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 0%, so the description must compensate for the lack of parameter documentation. It does not mention the 'limit' parameter at all, leaving its meaning and default behavior to inference. While 'limit' is a common term, the description adds no value beyond the schema's type and default.

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 uses a specific verb ('Return') and names a specific resource ('recent compact Director results from the runtime log'). It clearly indicates what the tool does, but does not explicitly differentiate from sibling tools like neo_director, leaving some ambiguity about when this vs. the main tool should be used.

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 guidance is given on when to use this tool versus alternatives such as neo_director or neo_collective. The description does not mention any prerequisites, exclusions, or conditions that would help an agent choose this tool over others.

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