buildUserContext

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not indicate whether the operation is read-only, whether it has side effects, requires authentication, or simply compiles already-fetched data. The lack of any mention of return format or operational characteristics leaves significant ambiguity for a tool with zero annotations and 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?

The description is a single, front-loaded sentence that efficiently conveys the core purpose and key included data points. Every phrase earns its place, and there is no redundant or filler content.

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 tool is simple (0 params, no output schema), so the description must cover what the tool does and what it returns. It lists the components of the compiled context, which helps, but it does not indicate what form the output takes (e.g., a summary object, a list) or how this tool relates to the sibling fetch tools. This is adequate for a basic understanding but leaves some gaps for an agent deciding whether to use this tool.

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 tool has zero parameters, so the schema provides no parameter semantics. Per the rubric, the baseline is 4 for a no-parameter tool. The description adds value by specifying the kind of context compiled, but since there are no parameters to explain, no additional compensation is needed.

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 'compile' and identifies a distinct resource: context about the user's current work state. It further lists concrete components (active project, meetings within the hour, key collaborators), clearly differentiating it from sibling tools that simply fetch notifications or perform calculations. The purpose is immediately understandable.

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?

There is no explicit guidance on when to use this tool versus alternatives. While siblings like fetchCalendarEvents or fetchGmailNotifications overlap with specific data sources, the description does not state that this tool should be used for a holistic overview before prioritizing, nor does it mention any exclusion criteria or alternative suggestions.

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