get_reports_retention

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

With no annotations, the description must disclose behavioral traits. It only states the action, leaving critical details unclear: is the operation read-only? Are there any side effects or permissions required? The agent cannot infer safety or limitations.

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, five-word sentence with no unnecessary words. It is front-loaded with the key information and is as concise as possible.

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 is a simple getter with no parameters and no output schema, the description could still benefit from mentioning what the retention settings include (e.g., time unit, default values) or confirming it returns a configuration object. The minimal description leaves the agent uncertain about the return value.

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 input schema has zero parameters, so 100% coverage is achieved. The description correctly implies no parameters are needed. Per guidelines, a baseline of 4 is appropriate since the description does not add meaning beyond the schema but does not contradict it.

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 'Get reports data retention settings,' which matches the tool name and specifies both the action (get) and the resource (reports data retention settings). It distinguishes itself from sibling tools like get_time_settings or get_admin_settings, though it could be more specific about which reports are involved.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., get_admin_settings for admin-level settings). There is no mention of prerequisites or context for invocation.

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