get_weekly_report

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuine behavioral trait — 'Deterministic' — implying repeatable, non-stochastic output, plus the content of the pending-queue metric. It says nothing about time window, caching, or cost, but with annotations and an output schema present the bar is lower.

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?

A single compact sentence, front-loaded with the primary deliverable and keeping the secondary metric subordinate in parentheses. No filler, though the telegraphic '+' construction is slightly terse relative to how much ambiguity remains.

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?

For a zero-parameter read tool with an output schema, the description does not need to enumerate return values, and it correctly signals that one of them is system pending-queue size. The main gap is selection guidance against the many report-like siblings, which the output schema cannot compensate for.

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 takes zero parameters, so per the rubric the baseline is 4. The description implies the report period ('weekly') without needing any argument, which is consistent with the empty schema.

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?

Names a concrete deliverable ('weekly report') plus a specific extra payload ('health metrics of the system itself (pending-queue size)'), so an agent knows this is an operational/system report rather than a clinical one. The phrase 'of the system itself' partially disambiguates from clinical siblings like get_health_summary and nutrition_report, but it never states the relationship explicitly.

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 when-to-use statement, no prerequisites, and no alternatives named. With siblings such as get_health_summary, nutrition_report, get_timeline and get_trend available, the agent gets no signal about when this tool is the right choice over those.

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