List wFirma contractors

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral detail beyond the scoping constraint 'for one explicitly selected wFirma client company,' which is more about usage context than behavior. It does not contradict the 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 a single, front-loaded sentence with zero wasted words. It states the verb, resource, and scope immediately, making it easy for an agent to parse quickly.

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 list operation, 100% schema coverage, and rich annotations, the description is nearly complete. It could explicitly mention pagination or that companyId comes from wfirma_list_companies, but the schema already provides that. The description adequately conveys the core operation and selection requirement.

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 description coverage is 100%, so the schema already documents all three parameters in detail, including the warning that companyId is an internal id from wfirma_list_companies and never a NIP. The description adds no additional parameter meaning beyond reinforcing that the company must be explicitly selected.

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 'List' with the resource 'contractors' and adds the crucial qualifier 'for one explicitly selected wFirma client company.' This clearly distinguishes it from listing all companies or getting a single contractor, and aligns with the required companyId parameter.

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 a usage precondition: the agent must have already selected a specific wFirma client company. It does not explicitly name alternatives like wfirma_get_contractor or wfirma_list_companies, but the 'one explicitly selected' phrasing gives clear context that this is not a cross-company listing tool.

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