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

No annotations are provided, so the description carries the full burden. It does disclose the payload difference between modes and warns that full mode is "large", which is useful behavioral context, but it says nothing about read-only safety, caching, or any cost/auth implications.

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 compact sentences with the resource named first and the mode semantics front-loaded; every clause carries information. The fragmentary phrasing ("The Basis methodology.") is efficient but not fully polished, keeping it below 5.

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?

With no output schema and no annotations, the description does the necessary work by outlining the returned content for both modes (index list, versions, component counts vs. formula, weights, specifications). It is sufficient for correct invocation, though a note on output format or size handling for full mode would round it out.

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 coverage is 0% and the schema does not even declare an enum for mode, but the description compensates fully: it defines both accepted values, states the default, and describes the content returned by each. This is exactly the case where the description must document the parameter, and it does.

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 names the specific resource (the Basis methodology) and what each mode returns, so an agent can tell it apart from sibling retrieval tools like basis_data or basis_answer. It lacks an explicit verb ("retrieve"/"get"), relying on the tool name to supply the action, which keeps it just short of a 5.

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?

It clearly explains the two modes and marks summary as the default, which is genuine selection guidance for the parameter. However, it gives no guidance on when to call this tool at all versus siblings such as basis_answer or basis_data, and no exclusions or prerequisites.

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