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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention any behavioral traits such as being read-only, requiring authentication, or any side effects. Given the zero-parameter input, the description is insufficient for understanding the tool's behavior beyond its purpose.

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 tool's purpose and usage order. Every word earns its place, and there is no unnecessary information.

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 that there are no parameters and no output schema, the description is minimal. It tells what the tool does and when to use it, but does not describe the return format or contents. For a simple introductory tool, this is adequate but could benefit from a brief note on what the context includes.

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 no parameters, so the schema coverage is 100% by default. The description adds no parameter information, but none is needed. The baseline score of 4 is appropriate as there is no room for improvement.

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 clearly states the action (get) and resource (pre-computed context about the timeshare index), and the phrase 'use this first' implies it provides orientation, distinguishing it from sibling tools. However, it does not specify what exactly the context contains, which could be more precise.

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?

The description explicitly advises 'use this first', giving clear guidance on when to invoke this tool before others. It does not mention when not to use it or provide alternatives, but the instruction is direct and useful.

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