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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds non-obvious semantics: 'null means unlimited' for both slots_left and reviews_left, that reviews_left is account-wide across all projects, that it resets at reviews_reset_at, and that limits are per-dashboard widget counts. It stops short of describing error behavior, which keeps it below 5.

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?

Front-loaded with the returned fields before the derived semantics, and each clause carries real information. It is dense and parenthetical-heavy ('(and widgets on each dashboard)'), which costs some readability but little is genuinely redundant.

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?

With no output schema, the description must explain the return payload and largely does: field meanings, null semantics, timezone/date basis, and limit accounting. Minor gaps remain around the response shape and how slots_left is calculated per resource, but an agent has enough to call and interpret it correctly.

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?

Schema coverage is 100% and the single parameter's schema description already explains the ID source, when it is required, and the API-key exception. The description restates the same defaulting behavior ('the API key's, or the one named by project') without adding format or syntax detail, so baseline 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?

States precisely what the tool returns: name, timezone, plan, retention days, today's date in project timezone, default 28-day range, currency, plan limits with usage, slots_left and reviews_left. It also disambiguates scope ('the API key's, or the one named by project'), so an agent can separate it from list_projects and get_overview.

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?

Gives an explicit directive: 'Call it first: every date in every other tool is a calendar day in this timezone.' That is a clear when-to-use rule tied to a concrete consequence, and the reviews_left note points to the related save_review tool.

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