linear_getManagedOAuthApplications

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

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint, covering safety and idempotency. Description adds behavioral context about ownership scope and CRUD limitations, which is valuable beyond 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?

Two sentences, efficiently front-loaded with core purpose, no unnecessary words. Perfect conciseness.

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?

Has output schema, so return format is covered. Description gives purpose and scope, but 'alpha child' is not explained, which could leave ambiguity. Otherwise sufficient for a zero-parameter listing 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?

No parameters (schema coverage 100%), so description does not need to add param info. Baseline 3 applies; no additional value provided or needed.

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?

Description clearly states it lists 'alpha child OAuth applications owned by the calling OAuth application' and distinguishes itself from a workspace-wide listing and generic CRUD. The term 'alpha child' is somewhat ambiguous, lowering clarity slightly.

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?

Explicitly states what it is not (workspace-wide admin listing, generic CRUD), guiding when not to use it. Does not name alternative tools but the exclusion is clear, and sibling getManagedOAuthApplicationById handles single retrieval.

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