Find Token

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

The description explains the search behavior (substring match, namespaces, example queries) beyond the readOnlyHint annotation. No contradictions; it adds useful context without needing to cover auth or rate limits given the read-only nature.

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 concise, front-loaded with the purpose, scope, examples, and a critical limitation. Every sentence adds value, and there is no redundancy.

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 search tool with one parameter and no output schema, the description covers all necessary aspects: search scope, matching behavior, examples, and a clear caveat. No gaps remain.

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 a single parameter. The description adds examples and a limitation (substring only on variable names), going beyond the schema's basic description. This provides meaningful additional guidance for the agent.

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 tool searches for design tokens by substring on variable name, specifying namespaces (--bsi-*, --it-*) and providing examples. It is distinct from sibling tools which focus on components or other functions.

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 indicates when to use the tool and provides explicit guidance on query behavior (substring only on variable names, with an example of what fails). However, it does not mention alternatives or explicitly state when not to use it.

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