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 provides no information about side effects, read-only nature, data source, return format, or any operational characteristics. The agent has no basis to understand what invoking this tool will do beyond the vague concept of a review cycle.

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 extremely concise, consisting of a single short phrase. It is appropriately sized for a tool with no parameters, and the key terms 'overdue and upcoming' are front-loaded. However, it is a noun phrase rather than a complete sentence, which slightly reduces clarity.

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 output schema and no annotations, so the description should explain what the agent can expect to receive. 'Policy review cycle — overdue and upcoming' gives only a high-level topic and does not clarify whether the result is a list, counts, dates, or next steps. Given the sibling tools (e.g., compliance_score, coverage_map), more context is needed to understand this tool's specific role.

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 is trivially complete. The baseline score is 4 because there are no parameters to document. The description adds no parameter-related information, but none 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 'Policy review cycle — overdue and upcoming.' indicates the tool's domain (policy reviews) and that it covers overdue and upcoming items, but lacks an action verb or explicit resource. It is somewhat vague and does not clearly distinguish from siblings like list_policies or compliance_score, though it hints at a scheduling-focused purpose.

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 guidance on when to use this tool versus alternatives like approval_tracker or policy_gap_check. The description mentions overdue and upcoming items, implying it might be used for tracking review dates, but no explicit when-to-use or exclusions are provided.

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