bulk_get_properties

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

The description contradicts annotations: it says 'retrieve' implying a read operation, but readOnlyHint is false. Additionally, no behavioral traits like property existence handling or rate limiting are disclosed, and with no annotation support, the description fails to clarify the tool's safety or reliability.

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 concise sentence front-loading the purpose. However, at only 10 words, it may be too brief to cover all necessary context, though it avoids unnecessary detail.

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 no output schema, the description does not specify return format (e.g., a dictionary of name-value pairs) or error handling. The tool's simplicity and the presence of many sibling tools demand more detail to ensure correct usage.

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%: the only parameter 'names' is fully described in the schema. The description adds no further meaning beyond the schema, so it meets the baseline without extra value.

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 'Retrieve multiple system property values in a single call' clearly states what the tool does with a specific verb (retrieve) and resource (system property values). It effectively distinguishes from related tools like get_system_property (single property) and set_system_property.

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 such as get_system_property or other bulk retrieval tools. No mention of context clues like batch size limits or scenarios where a single call is preferable.

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