trmnl_get_mashup

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds that sections are returned alongside the mashup, which is useful since there is no output schema, but says nothing about authorization, error behavior, or the shape of sections.

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?

Two short sentences, with the functional statement front-loaded and the endpoint reference trailing. Nothing is wasted, though the API path line adds little for an agent that already has the tool name.

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 read tool with annotations and no output schema, returning 'mashup and its sections' is enough to call it, but the description never explains what a mashup or a section is, and it leaves the nested path object and optional profile unaddressed. Adequate, not complete.

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?

Both the nested path.id and the optional profile are already documented in the schema, so the description adds no parameter meaning beyond what is structured. The description does not clarify that 'id' is the path parameter, leaving the nested-object requirement to the schema alone.

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?

States a specific verb and resource: 'Read a mashup and its sections', which tells the agent exactly what comes back. It does not differentiate from nearby siblings like trmnl_get_mashup_options, trmnl_get_mashup_timeline, or trmnl_update_mashup, but the core action is unambiguous.

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 on when to use this instead of trmnl_get_mashup_options, trmnl_get_mashup_timeline, or trmnl_update_mashup, all of which operate on the same resource family. The agent must infer selection from the name alone.

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