logicstamp_read_logicstamp_docs

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

With no annotations provided, the description carries full burden. It transparently describes the tool's output (documentation bundle) and content areas (what LogicStamp is, workflow, best practices). It does not mention side effects or authorization, but as a read-only documentation tool, this is acceptable.

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 appropriately sized and front-loaded with the main purpose. However, it repeats some information (e.g., 'Explains' section overlaps with earlier list) and could be slightly more concise without losing clarity.

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 zero parameters and no output schema, the description fully covers what the tool does, when to use it, and what it returns. It addresses all likely information needs for an agent selecting this 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?

The input schema has zero parameters, so the description only needs to explain the tool's function. It does so comprehensively, listing the documentation contents and use cases, adding significant meaning beyond the empty schema.

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 clearly states the tool returns comprehensive LogicStamp documentation, listing specific contents (guide, usage, contracts, schema, CLI, limitations). It distinguishes from sibling tools that focus on comparing modes, snapshots, or reading specific bundles, establishing unique value.

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 explicitly states when to use the tool ('unsure how LogicStamp works, starting new project, need bundle structure/contract format') and includes an 'escape hatch' for confusion. While it provides clear context, it does not explicitly state when not to use it or alternatives, though sibling differentiation is implicit.

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