axon_pro_related_files

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only lookup through the verb 'Find' but does not disclose permissions, side effects, output format, missing-file behavior, or what constitutes structural versus temporal coupling.

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 wasted words. It states the action, resource, and relational scope immediately.

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?

For a simple one-parameter lookup tool, the description is minimally adequate. However, without annotations or an output schema, it leaves behavioral and interpretive gaps—particularly around what structural/temporal coupling means and what the returned file list represents.

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% for the single parameter, and the schema already documents 'file_path' as the path to the reference file. The description adds no syntax, format, or constraint details beyond the schema, so the baseline score of 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 description uses a specific verb ('Find') and resource ('files') and adds a clear relational qualifier ('structurally or temporally coupled to a given file'). It is distinguishable from generic search tools, though it does not explicitly name or contrast with sibling tools such as axon_pro_context or axon_pro_impact.

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 states what the tool does but gives no explicit guidance on when to use it, when not to use it, or which sibling tools are alternatives. The implied usage is present only through the tool's purpose, similar to a minimally documented mutation tool.

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