linear_getCustomers

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no additional behavioral context (e.g., pagination, sorting defaults, rate limits). Since annotations cover safety, the description is adequate but not enhanced. No contradiction.

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). It is front-loaded and wastes no words. However, it could be structured better to include key information like that it returns a list of customers. Still, it is appropriately sized for a simple retrieval operation.

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?

Despite having a full parameter schema and output schema, the description is minimal. It doesn't explain that this is a list endpoint, that multiple filters can be combined, or that default sorting or limit apply. For a tool with 8 optional parameters and many sibling tools, the description leaves out important context for proper usage.

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% for all 8 parameters, each with clear descriptions. The tool description does not add any extra meaning or usage hints beyond the schema. Thus it meets the baseline expectation but provides no added 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 'Get customers from Linear' clearly states the action and resource. However, it doesn't distinguish from sibling tools like 'getCustomerById' or 'getCustomerNeeds', which also retrieve customer data but with different scope. The purpose is clear but lacks differentiation.

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?

No guidance on when to use this tool versus alternatives like 'getCustomerById' for a single customer or search endpoints. The description does not mention filtering capabilities or usage context (e.g., listing all customers). An agent would have to infer usage from the tool name alone.

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