zero_read

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

With no annotations, the description carries the full burden. It discloses access control and audit behavior (T1/T2 tiers), but does not mention side effects or that it is a read-only operation. Partial behavioral disclosure.

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 concise at one sentence, but the use of undefined abbreviations (T1, T2) and lack of up-front clarity on parameter reduce effectiveness. It is brief but could be more self-contained.

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 complexity of access tiers and a single undocumented parameter, the description is incomplete. It does not explain output format, error states, or how the tier system works, leaving significant gaps for an agent.

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 single parameter id_or_alias is not explained in the description and the schema provides no description (0% coverage). The agent has no guidance on what values are valid or the format expected.

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 reads notes including frontmatter and body, distinguishing it from sibling tools like zero_write_note and zero_search. However, the use of cryptic abbreviations T1 and T2 reduces clarity for those unfamiliar with the system.

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 mentions conditions (T1 audit, T2 approval) but does not explicitly state when to use this tool versus alternatives or provide exclusions. Usage context is implied from the tool's purpose.

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