List Company Inactive Users

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint. The description adds valuable context: paginated JSON array, pagination metadata, page/per_page usage, and a link to filtering documentation. It does not contradict annotations.

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?

Five well-structured sentences, front-loaded with purpose. Each sentence adds value: purpose, link to docs, usage scenarios, return type, pagination control, required param, API identification. No redundant information.

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?

The description covers purpose, usage, pagination, and required parameters. No output schema exists, but the description mentions 'paginated JSON array of Directory records' which is sufficient. The annotations and schema fill gaps. Slightly lacks detail on record structure, but acceptable for this simple list 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?

Input schema has 100% description coverage for all 4 parameters. The description repeats 'Required parameters: company_id' but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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 it returns a list of all Inactive Users for a company, using specific verb 'Return' and resource 'Inactive Users'. It distinguishes from siblings like 'list_company_users_v1_3' by specifying 'inactive' and from 'list_company_inactive_vendors' by specifying 'users'.

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 provides explicit usage scenarios: 'enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters'. It does not explicitly say when not to use it, but the context and sibling tools implicitly differentiate usage.

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