Get DM rate limit status

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

With no annotations, the description carries the full burden. The verb 'Show' clearly indicates a read-only operation, which is transparent. However, it does not disclose whether the call itself consumes rate limits, any authentication requirements, or how 'local' usage is determined, leaving some behavioral traits implicit.

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 efficient sentence that immediately states the action and resource, followed by helpful specifics. No words are wasted, and the information is front-loaded.

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?

Despite having no output schema or annotations, the simple zero-parameter nature of the tool is well-served by this description. It covers the purpose and lists the key data points, though it stops short of specifying the exact output format or units, which would be useful for parsing the response.

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, and the schema correctly reflects that. The description adds no parameter information, but none is needed. For a zero-parameter tool, the baseline is 4, and the description adequately supports this.

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 uses the specific verb 'Show' with the resource 'local DM send rate limits' and details the exact metrics (hourly, daily, min interval). This clearly distinguishes it from sibling DM tools, which focus on sending, drafts, and inbox management rather than rate limits.

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 description implies this tool should be used for checking DM rate limits and current usage, but it does not explicitly state when to use it or provide exclusions/alternatives. There are no sibling rate-limit tools, so the context is inferred rather than stated.

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