likeSelectMaterielList

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

Describes reading form config, querying an endpoint, and using data dictionary. No annotations exist, so description carries full burden. It implies read-only but doesn't explicitly state safety, auth requirements, or rate limits. Adequate but missing some details.

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?

Three sentences front-loaded with main action and process details. Every sentence adds value without redundancy. Concise and well-structured.

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?

Lacks output schema and annotations. Description explains internal logic but does not detail the return format (e.g., fields in material records). For a query tool, the agent may need to know what properties are available. Gaps in safety and output details reduce 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 covers 100% of parameters. Description adds value by explaining the process (reading form config) which gives context to contain/exclude parameters, and the filters parameter is well-described. The description enhances understanding beyond schema.

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 it queries material lists with dynamic pagination according to MES form configuration. It specifies the endpoint, data dictionary translation, and a specific use case (before uploadSop). This distinguishes it from siblings which query SOPs, tasks, workstations, etc.

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?

Explicitly states to use before uploadSop to retrieve materielId. While it doesn't explicitly list when not to use, the context implies it's for material queries, and siblings handle other entities. Clear usage context is provided.

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