views_create

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Record a document view' without mentioning side effects, idempotency, permissions, or whether it creates a duplicate each time. This is comparable to the update_drive example where mutation details are omitted.

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 front-loaded, but the brevity results in under-specification. While there is no wasted text, the tool could benefit from additional context, making it minimally adequate but not ideal.

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 has no annotations, no output schema, and a 4-word description. The agent is left without information on return values, side effects, or how this interacts with related tools. Given the low complexity, this is still a significant gap.

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 schema covers the single parameter 'documentId' with a description, meaning 100% coverage. The tool description adds no extra meaning beyond the schema, so the baseline score of 3 applies.

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 'Record a document view' uses a specific verb ('Record') and a clear resource ('document view'), indicating a write operation that logs a view. It distinguishes itself from sibling 'views_list' by implying an action rather than a listing, though it could be slightly ambiguous whether it creates a saved view or logs an event.

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 provided on when to use this tool versus alternatives such as 'documents_viewed' or 'views_list'. There is no mention of prerequisites, exclusions, or contextual triggers.

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