disasm.linear

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic purpose without indicating whether the operation is read-only, requires specific permissions, or has any side effects. This is insufficient for an agent to understand the tool's impact.

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 short but wastes the opportunity to convey critical information. It is under-specified rather than efficiently concise; every word is present but fails to earn its place due to lack of detail.

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 presence of three parameters, no output schema, and many similar sibling tools, the description is completely inadequate. It provides no information about the return format, the scope of disassembly, or how to interpret parameters, resulting in poor contextual completeness.

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 0%, meaning the description adds no meaning to any of the three parameters (session_id, limit, offset). The description does not explain what these parameters control (e.g., what limit or offset refer to in the context of disassembly lines).

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 linear disassembly lines' names a verb and resource but is vague about what 'linear disassembly lines' means and how it differs from siblings like 'disasm.function' or 'disasm.range'. No scope or context is provided, making it unclear what the tool actually retrieves.

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 is given on when to use this tool versus any alternative. With many sibling tools related to disassembly and analysis, the lack of usage context forces the agent to guess or infer applicability.

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