foundry_select_tokens

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

Annotations only provide readOnlyHint=false. The description does not disclose side effects, such as whether selection is overwritten, whether it affects server state, or any permission requirements. No behavioral context beyond the annotation is given.

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 short sentence, which is concise in length, but it is under-specified for a tool with 7 parameters. It fails to earn its place as a useful guide.

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?

Given the tool's complexity (7 params, nested object, no output schema) and the availability of sibling tools, the description is severely incomplete. There is no explanation of return values, selection semantics, or parameter behavior.

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 description adds no information about the parameters. The schema has 7 optional properties with low coverage (43%), and the 'data' field is described only as 'JSON object accepted by Foundry,' which is unhelpful. The description does not explain how uuids, name, all, or overwrite work.

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 'Select tokens in the Foundry client', giving a specific verb and resource. However, 'select' is ambiguous (set vs. retrieve) and no differentiation is made from sibling foundry_get_selected_tokens, so it lacks sibling differentiation.

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 provides no guidance on when to use this tool, no mention of alternatives (e.g., get_selected_tokens), and no exclusions. It simply states what it does without context.

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