get_config_properties

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

The description mentions sensitive values are redacted, a key behavioral trait beyond the endpoint name. However, with no annotations, the description carries full burden but does not disclose read-only nature, potential errors, or response format. It adds modest value.

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 succinct sentence with no extraneous words. It efficiently communicates the core action and a notable trait (redaction).

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 the complexity of the sibling set (many actuator endpoints) and the lack of annotations, output schema, or parameter descriptions, the description is too sparse. It omits return structure, usage context, and parameter semantics, leaving significant gaps for an agent.

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?

The only parameter 'application' has no description in the schema or the tool description. With 0% schema coverage, the description fails to explain what this parameter does, leaving the agent without necessary context to use it effectively.

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 states it reads the /actuator/configprops endpoint with sensitive values redacted, clearly indicating the action and resource. However, it doesn't explain what configprops contains compared to other property-related tools like get_env_properties, which could cause confusion for agents unfamiliar with Spring Boot nomenclature.

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., get_env_properties, get_info). The absence of when-to-use, when-not-to-use, or alternative recommendations leaves the agent without direction.

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