context.mesh_select_mode

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

With no annotations, the description carries full burden but provides no behavioral details. It doesn't disclose whether it requires being in edit mode, how it affects existing selections, or any side effects. The description is too minimal for adequate transparency.

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 extremely concise at four words, with no superfluous information. It is front-loaded and clearly communicates the tool's purpose immediately.

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 simple nature of the tool (one enum parameter, no output schema), the description is minimally adequate. However, it lacks context like the requirement of edit mode or the effect on selection. A sentence about when it is applicable would improve completeness.

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 description coverage is 0%, so the description must compensate. However, it adds no additional meaning beyond the schema's enum values. The enum values are self-explanatory, but the description does not elaborate on them, leaving a 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?

Description clearly states 'Set mesh edit selection mode' with a specific verb and resource. It distinguishes from siblings like 'context.mode_set' and 'mesh.select_all' by being specifically about selection modes in edit mode.

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 on when to use this tool versus alternatives. For instance, it doesn't mention that it should be used only in edit mode or that 'context.mode_set' sets the overall mode. The agent receives no context on prerequisites or exclusions.

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