read_think_md

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

With no annotations, the description carries the behavioral burden, and 'read complete content' clearly indicates a read-only retrieval of the whole file. However, it does not mention return format, error behavior if think.md is missing, or whether the call has any side effects, though for a simple read operation the core behavior is stated.

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 short sentence with no filler. The operation and resource are front-loaded, and every word contributes meaning.

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?

For a zero-parameter, low-complexity read tool, the description is mostly complete: it identifies the exact resource and the scope of the read. The lack of output-format details is a minor gap since there is no output schema, but 'complete content' sufficiently answers most invocation needs.

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 tool has zero parameters, so there is no parameter semantics to clarify; the schema is already trivially complete. The description reinforces that the target is fixed to think.md and that no user choices are 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?

The description states a specific operation ('read') and a specific resource ('think.md'), and specifies that it returns the complete content, so the agent knows exactly what the tool targets. It does not explicitly contrast with siblings like get_think or write_think, so it stops short of full sibling differentiation.

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 gives no guidance on when to prefer this tool over alternatives such as get_think or write_think. The only implied usage is that it is for retrieving the full contents of think.md, but no exclusions or routing cues are provided.

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