List Project Inactive Vendors

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

Annotations (readOnlyHint, idempotentHint) already indicate safe read-only behavior. The description adds that it returns a 'paginated JSON array of Directory records' with pagination metadata, which clarifies the output format. No contradictions with 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?

The description is four sentences, front-loaded with the core purpose, then use-cases, pagination details, and API context. Every sentence adds value 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 100% schema coverage and annotations, the description covers the typical needs for a list endpoint: purpose, pagination, required parameter, and API reference. It does not define 'Directory records' but the schema and sibling tools provide additional context.

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%, so the schema already documents all parameters with descriptions. The description mentions page and per_page for pagination but does not add new parameter semantics beyond what the schema provides. Minimal additional value.

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 'Return a list of all Inactive Vendors associated with a Project,' specifying the verb (list), resource (inactive vendors), and scope (project). It distinguishes from siblings like list_company_inactive_vendors and list_project_vendors by emphasizing 'project' and 'inactive.'

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 gives context for use: 'enumerate Directory records when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not explicitly state when not to use or suggest alternatives, but the context implies it is for inactive vendors specifically.

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