yaaif_skill_read_file

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. The only behavioral clue is the verb 'read', implying a non-mutating operation, but it does not state what is returned, whether it is idempotent, permissions required, or error behavior. This adds little beyond the tool name.

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, front-loaded sentence with no unnecessary words. It immediately communicates the core action and resource without fluff.

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?

This is a simple one-parameter tool, but since there is no output schema or annotations, the description should explicitly mention the return value (file contents) and clarify path semantics. It leaves an agent guessing about the output format and how to construct a valid path, making it incomplete.

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 a `path` string with no description (0% coverage). The description adds some meaning by clarifying that the path refers to a file within the 'tenant skills tree', which gives an agent a namespace for the path. However, it does not explain the expected path format or whether it is relative/absolute, leaving partial compensation.

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 states a specific action ('Read') and a specific resource ('skill pack file') within a defined scope ('tenant skills tree'). It is clear and distinct from write/list siblings, though it does not explicitly contrast itself with similar reading tools like yaaif_skill_file_tree or yaaif_file_load_context.

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 provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as obtaining a valid path via yaaif_skill_file_tree, nor does it indicate scenarios where another tool should be preferred.

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