find_xcresults

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

Without annotations, the description carries the burden of behavioral disclosure. It only states that the tool finds files with timestamps and file information but does not mention any side effects, search scope (recursive?), or whether it requires specific permissions. This is minimal transparency for a file-finding tool.

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 sentence that immediately conveys the tool's purpose and output content. It is perfectly concise with no unnecessary words, and the structure is front-loaded and clear.

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?

There is no output schema, so the description must compensate by detailing what is returned. It mentions 'timestamps and file information' but lacks specifics such as data types, order, or whether paths are relative/absolute. Critical context like search scope (e.g., entire filesystem or project directory) is omitted, leaving the agent guessing.

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 input schema covers 100% of parameters, with the single parameter 'xcodeproj' described inline. The description does not add meaning beyond the schema for the parameter; it only mentions output features. Baseline 3 is appropriate since schema coverage is high and no parameter semantics are missing.

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 the verb 'find' and resource 'XCResult files for a specific project', which distinguishes it from sibling tools that perform operations on the content of such files (e.g., xcresult_browse, xcresult_list_attachments). The specificity of 'with timestamps and file information' adds clarity.

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. For example, it does not suggest that this should be used before other xcresult tools to locate files, nor does it mention when not to use it (e.g., if browsing contents is needed).

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