get_recent

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool gets entities, giving no information about safety (read-only vs. destructive), authorization needs, rate limits, or pagination behavior beyond the limit parameter. The description is insufficient for understanding the tool's full behavior.

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 sentence with no waste, but it is excessively brief. It lacks structure (e.g., sections or examples) and fails to provide enough information for effective use. Conciseness without completeness is not sufficient.

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?

Given the tool has one parameter and no annotations or output schema, the description should cover behavior and usage more thoroughly. It omits details like which entities are considered, sorting order, or whether the limit is a hard maximum. The description is minimally adequate at best.

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% with a single parameter 'limit' fully described. The description adds no meaning beyond the schema, so baseline score of 3 is appropriate. No additional context like format or constraints is provided.

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 'Get' and resource 'entities' with a clear qualifier 'most recently updated', distinguishing it from siblings like 'query_by_time' or 'search_nodes'. However, it lacks specificity about what constitutes 'recently updated' (e.g., timestamp field), leaving some ambiguity.

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 on when to use this tool versus alternatives. No exclusions or usage context provided. The description implies usage for fetching recent entities but offers no help in deciding between this and similar tools like 'query_by_time'.

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