basedpyright

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

There are no annotations provided, so the description must carry the full burden of behavioral disclosure. The description offers no information about side effects, file modifications, network access, or permissions required. It simply says 'Run', which is minimally informative and does not disclose any behavioral traits.

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 sentence and front-loaded, but it is under-specified rather than genuinely concise. It omits necessary context about parameters and behavior, so the brevity does not serve the agent well.

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 tool has one parameter, an output schema (per context), and no annotations, the description is incomplete. It does not explain what 'diagnostics' entails, how the output is structured, or how the 'paths' parameter affects behavior, leaving major gaps for correct invocation.

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?

The schema has one parameter 'paths' with 0% description coverage, and the tool description does not mention it at all. The description fails to explain what 'paths' means, how it should be provided, or its default behavior, offering no compensation for the lack of schema descriptions.

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 'Run basedpyright diagnostics' clearly identifies the tool's action ('Run') and resource ('basedpyright diagnostics'). It is specific enough to convey its purpose, but it does not explicitly differentiate from siblings like pytest or ruff_lint, though the name itself implies a type-checking focus.

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 no guidance on when to use this tool versus alternatives (e.g., pytest or ruff_lint), no prerequisites, and no exclusion criteria. It only states what the tool does, leaving the agent to infer appropriate usage scenarios without support.

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