bulk_get_properties

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

Description claims a read-only operation ('Retrieve'), but annotations have readOnlyHint=false, which suggests the tool may not be read-only. This is a contradiction. The description does not clarify the discrepancy or provide additional behavioral context beyond the structured annotations.

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?

Single concise sentence that front-loads the purpose and scope. Every word earns its place.

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?

For a simple retrieval tool with one parameter and no output schema, the description is minimally sufficient. However, the contradiction with annotations detracts from completeness, and no information is given about response format or error handling.

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% with one parameter 'names' described as 'Array of property names to retrieve'. The description adds no additional semantics beyond the schema, earning the baseline score of 3.

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 the action 'Retrieve multiple system property values' and specifies the resource 'system property values' and the scope 'in a single call'. It distinguishes from siblings like 'get_system_property' (single) and 'bulk_set_properties' (write).

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?

Description implies usage when needing multiple properties in one call but does not explicitly state when to prefer over alternatives like 'get_system_property' or 'list_system_properties'. No exclusion criteria or prerequisite information provided.

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