emacs_org_read

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

With no annotations, the description carries the behavioral burden. 'Read' clearly implies a non-mutating operation, and 'optional parsed structure' discloses a key output behavior. However, it does not explain the shape of the parsed structure, buffer assumptions, or possible errors, so some transparency gaps remain.

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 one clear, front-loaded sentence with no filler. It expresses the core read operation and the raw/parsed choice without repeating schema details.

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?

The tool is simple and the schema fully documents its two parameters, so the basic call is invokable. But there is no output schema, no annotation support, and no clarification of what a 'parsed structure' looks like, leaving interpretation of the result partially underspecified.

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 100%, so both buffer and format are already documented. The description adds the word 'optional' and implies the raw default, but it does not provide materially deeper parameter semantics than the input 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 uses the specific verb 'Read' and the resource 'org document content', and it adds 'optional parsed structure' to clarify the output mode. It does not explicitly contrast itself with emacs_buffer_read or emacs_org_search, but the org-specific scope and format option are enough to identify its role.

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 about when to choose emacs_org_read over emacs_buffer_read or emacs_org_search. The description and schema only explain what the tool does, not when it is the right tool among many similar siblings.

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