where_used

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

With no annotations, the description must carry behavioral context. It discloses that the tool lists referencing files and implies a read-only search operation, but it does not state permissions, limitations, or behavior when no references exist. Some useful context is present, but the disclosure is not comprehensive.

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 concise sentence that front-loads the core action and scope. There is no filler, and every word contributes to the meaning.

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 listing tool with an output schema, the description covers the essential purpose and scope. It is slightly under-specified regarding permissions and edge-case behavior, but the presence of an output schema reduces the need to document return values.

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 only says stanza_id is a string, and schema description coverage is 0%. The description adds meaning by indicating that this parameter identifies the stanza whose references are sought, but it does not explain the expected format, source, or how to obtain a valid stanza_id. It partially compensates for the schema gap.

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 ('List') and resource ('project map and role file') and specifies the search object ('a stanza'). It clearly conveys what the tool does and implicitly differentiates it from the sibling where_used_skill by targeting stanzas rather than skills, though it does not name that sibling explicitly.

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 intended use case is implied: use this tool when you need to find project maps and role files that reference a given stanza. However, the description does not explicitly state when to prefer this tool over alternatives such as where_used_skill, nor does it provide any exclusion conditions.

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