export_properties

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

Annotations already provide readOnlyHint=true and openWorldHint=true, indicating safe read operation and potential dynamic state. The description adds the 'environment snapshots' context but does not disclose additional behavioral traits like what happens with empty query, output format, or rate limits. No contradiction with 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?

The description is a single, front-loaded sentence that captures the core action and use case without unnecessary words. Every part 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?

The description covers purpose and use case but lacks details on output format, default behavior when query is omitted, and whether all properties are exported if no query is provided. Given no output schema and optional parameters, more completeness would help.

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 both parameters (query, category) described. The description mentions 'matching a query' which aligns with the query parameter, but does not add semantic value beyond the schema's descriptions. Baseline 3 is appropriate.

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 tool exports system properties matching a query to a JSON object, with a specific use case (environment snapshots). This distinguishes it from sibling tools like list_system_properties which list properties, and get_system_property which retrieves a single 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 a use case (environment snapshots) but does not explicitly guide when to use this tool over alternatives like list_system_properties, get_system_property, or search_system_properties. It lacks when-not-to-use and exclusion criteria.

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