read

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It mentions 'newest first' and default max_entries, but does not state that this is a safe read-only operation, how prefixes are matched, or any error/edge-case behavior. The description adds only minimal behavioral context.

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 one-sentence summary plus a concise, well-structured argument list. Each line provides necessary information with no redundancy or filler. The format is easy to scan and front-loads the purpose.

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 description adequately covers parameter meanings for a tool with moderate complexity and an output schema. However, it lacks usage context, behavioral caveats, and explicit differentiation from siblings, leaving overall completeness somewhat shallow.

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 schema has 0% description coverage, so the parameter documentation in the description is essential. It explains each parameter with domain-specific details (e.g., role is for sessions, speaker for transcripts) and notes defaults and ordering behavior. This adds significant meaning beyond the bare 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 'Read entries from a domain file', which is a specific verb and resource. It conveys the core action and target, but does not explicitly differentiate from siblings like 'search' or 'list_domain', leaving some ambiguity about when 'read' is the right choice.

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 provides no guidance on when to use this tool vs alternatives. It only documents parameters, with no mention of use cases, prerequisites, or exclusions. Sibling tools are not referenced or contrasted.

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