List All Company Managed Equipment User Permissions

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

Annotations indicate readOnlyHint=true, etc. The description adds value by disclosing pagination behavior (page, per_page, pagination metadata), the required company_id, and the API endpoint. It does not cover rate limits or error handling, but the added context is significant.

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 action, followed by usage guidance, return format, pagination control, and required parameters. Every sentence is informative and free of fluff.

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?

Without an output schema, the description should describe the response structure more thoroughly. It mentions 'paginated JSON array of Field Productivity records' but does not detail the fields or properties of each record. This leaves some ambiguity for the agent.

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 already has clear descriptions for all three parameters (100% coverage). The description reinforces that page/per_page control pagination and that company_id is required, and adds context about response metadata. This provides additional meaning beyond the schema.

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 the tool returns a list of all Company Managed Equipment User Permissions for a specified company. It uses a specific verb ('Return a list of') and identifies the resource, distinguishing it from other list tools on the server.

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 context: 'Use this to enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters.' It does not mention when not to use or list alternatives, but the guidance is clear and helpful.

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