read_store_file

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: no permission requirements, no indication of what happens on a missing path, no return format, no size limits. Only the word 'Read' hints at a non-destructive operation.

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?

It is short, but brevity here reflects under-specification rather than conciseness — the single cryptic fragment omits everything an agent needs and wastes space on the meaningless 'Extended:' prefix.

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?

With no annotations and no output schema, the description must compensate and does not. For a two-required-parameter file read tool, an agent cannot tell the expected path root, error behavior, or output shape from this text alone.

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%, and the two parameters (storeId, relativePath) are documented in the schema, including an example path. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 string 'ReadAgentStoreFile' conveys a read operation against a store file, and the parenthetical '(Project Context / shared notes)' hints at the content domain. However, the 'Extended:' prefix is internal jargon that adds no meaning, and the description never states in plain language what the tool returns or how it relates to siblings like get_blob or list_workspace_files.

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?

There is no guidance on when to use this tool versus the many sibling listing/fetching tools (list_agent_stores, list_workspace_files, get_blob). The only hint is the implicit pairing of storeId + relativePath, which the agent must infer on its own.

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