trmnl_get_installation_configuration

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

Annotations already cover readOnly, idempotent, non-destructive and openWorld, so the safety profile is known without the description. The description adds only the hint that the configuration is "pending", which is never explained (pending what – setup? approval?), and says nothing about permissions or what the call returns for an unconfigured installation.

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?

It is short and front-loaded with the verb, so it is not padded. But the second line is a raw REST path pasted in, which is low-value for an agent and half the description's length is spent on it.

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 nested-parameter, no-output-schema read tool, the definition leaves out what a configuration payload contains and how the required installation ID is obtained. The annotations carry the safety story, but the functional story is largely absent.

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 50%: the nested required plugin_installation_id is a bare UUID string with no description, and only the optional profile field is documented. The description does not compensate – it neither explains where to get the installation ID nor what the profile selector changes.

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 verb+resource ("Read ... configuration") plus the raw endpoint path make it possible to infer this fetches a plugin installation's configuration, but "pending configuration" is ambiguous wording and the name/description do not distinguish it from close siblings such as trmnl_get_plugin_configuration or trmnl_get_installation_configuration_choices. An agent cannot tell from this text alone which configuration resource it needs.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. With siblings like trmnl_update_installation_configuration and trmnl_evaluate_installation_configuration in the list, the absence of routing guidance forces the agent to guess.

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