mesh.select_by_index

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'Select' without mentioning the default action (REPLACE), whether it works in edit mode, or how it interacts with existing selection. This is a significant gap.

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 very concise (one sentence) but at the expense of completeness. It is front-loaded with the core purpose, but every sentence should earn its place; here, more sentences are needed for adequate guidance.

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 4 parameters, 2 enums, and no annotations or output schema, the description is too brief. It fails to explain the action parameter, the mode parameter, or the required object parameter. Compared to similar tools, it lacks essential context for proper use.

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?

With 0% schema description coverage, the description should clarify parameter usage. It does not mention the 'indices' format (comma-separated?), the 'mode' enum values, or the 'action' parameter. The schema titles provide some meaning, but the description adds no additional clarification.

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 verb 'Select', the resource 'mesh elements', and the method 'by zero-based index'. This distinguishes it from sibling tools like mesh.select_all (select all) or mesh.selection_report (report selection).

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 versus alternatives (e.g., mesh.select_all) or when not to use it. It lacks context for decision-making.

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