Retrieve TNL

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

Annotations provide readOnlyHint=true, so the description's 'Return' aligns. Additionally, the description discloses that IDs with no matching file are listed in notFound, which adds value beyond annotations by warning about missing resources.

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?

Two sentences with no waste; front-loaded with the core action, then adds the critical edge case about notFound.

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?

Simple tool (one param, no output schema), so description is sufficient. Could optionally mention output format but not required. Edge case handling is included.

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 coverage is 100% with clear description for the 'ids' parameter, and the description adds context that it's verbatim content and that missing IDs appear in notFound, enhancing understanding.

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 verb ('Return') and resource ('verbatim content of TNL units identified by id'), and distinguishes from siblings by focusing on retrieval rather than modification or analysis.

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?

Implied usage from context, but no explicit guidance on when to use this vs. alternatives like 'trace' or 'get_impacted_tnls' for similar TNL-related tasks.

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