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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond them by specifying the shape of the returned data (per-weekday open flag, start/end of working day), which matters since there is no output schema.

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?

One front-loaded sentence captures the return content and its purpose, followed by the endpoint path. The raw HTTP path adds little for an MCP consumer but costs only a few tokens, so it is not a meaningful defect.

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 parameters and no output schema, the description carries the return-value burden and does so at a reasonable level of detail (per weekday, open flag, start/end). Only finer details such as time format or timezone are omitted.

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 and the description correctly says nothing about inputs, so there are no parameter semantics to clarify. Baseline of 4 applies for a parameterless read.

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 names the specific resource (per-weekday store operating hours with open flag, start and end) and adds the downstream purpose (pickup and delivery estimates). It is unambiguous about what is returned, though it does not explicitly contrast with siblings like shippit_estimate_delivery_dates, which consume this data.

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 mention that these are the hours Shippit uses for pickup and delivery estimates implies why an agent would fetch them, but there is no explicit when-to-use or when-not-to-use guidance, nor any stated prerequisites. Usage must be inferred.

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