Cache Org Users

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

Annotations already indicate idempotent and non-destructive behavior. The description adds transparency by stating it caches to disk and returns cache metadata with a resource URI. No contradictions; the side effect (writing to disk) is disclosed.

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 extremely concise: one sentence for purpose, an Args list, and a Returns line. No unnecessary words; every part earns its place.

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 tool with 3 optional parameters and an output schema, the description fully covers what the tool does, its parameters with defaults, and what it returns (cache metadata with resourceUri). No missing information.

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 description adds value by summarizing default values (pageSize defaults to 250, max 500; orderBy defaults to id; orderByDirection enforces 'asc' or 'desc'). This goes beyond the schema by providing defaults in a concise format.

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 clearly states 'Fetch and cache all organization users to disk for efficient repeated access.' This specifies a verb (fetch and cache), a resource (organization users), and a distinct purpose (efficient repeated access). Among siblings, list_org_users likely provides one-time listing, so this tool is well-differentiated.

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 when to use: for caching users to avoid repeated fetches. However, it does not explicitly mention when not to use or alternatives (e.g., list_org_users for one-time access). The context is clear but lacks explicit exclusions.

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