owp_repo_read

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

With no annotations, the description carries the full burden of behavioral disclosure, but it merely states the forwarding action without noting whether this mutates state, requires auth, or has other consequences. The name implies a read operation, but the description does not confirm safety or side effects.

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 clear sentence followed by a terse parameter list; every element earns its place with no redundancy. The front-loaded action and structured args make it easy to parse.

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 covers the parameters, but for a tool with no annotations, it lacks usage context and behavioral details such as when to invoke this forwarder and what the ledger coordinator does with the payload. The existing output schema reduces the need for return documentation, but other gaps remain.

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 provides only names and string types (0% description coverage), so the description compensates by explaining 'ledger' as a path to a SQLite ledger file and 'payload' as a JSON string of the execution payload. This adds meaningful semantics beyond the 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 opening sentence clearly states the action ('Forward a repo-read execution') and target ('to the ledger coordinator'), distinguishing it as a forwarding operation among related repo tools. It is specific and unambiguous, though it does not explicitly contrast with siblings.

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 on when to use this tool versus alternatives like owp_analyze_repo or owp_get_schema; it only describes the action, leaving the agent to infer context. There are no exclusions or conditions stated.

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