Get Org Limits and Usage

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

Annotations already establish the read-only, idempotent nature. The description adds behavioral detail beyond annotations: it returns all limits sorted by percent used, and describes the output fields (name, remaining, max, percentUsed). It doesn't mention error cases or response size, but for a safe read tool this is sufficient.

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 compact: two sentences plus a bulleted use-case list. It front-loads the main action, then adds useful context without redundancy.

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 simple read-only nature, rich annotations, and complete parameter schema, the description covers the essential return format and use cases. It doesn't discuss edge cases like filtering case-sensitivity or empty responses, but these are minor gaps for this tool.

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% (the single optional 'filter' parameter is described in the schema). The description itself doesn't elaborate on the filter behavior; it only says 'Returns all limits,' while the schema already documents the substring match. 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?

The description opens with a specific action ('Retrieves current API and governor limit usage') and names the resource ('Salesforce Limits REST API'), clearly distinguishing it from the creation/management tools in the sibling list. It also states the exact return type.

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 'Useful for' list provides explicit scenarios (checking API call usage, monitoring storage, etc.) that tell an agent when to invoke this tool. It lacks explicit exclusions or named alternatives, so it doesn't reach 5.

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