tm_get_profile

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

The description details the return value (name, RPS curve, etc., and run status) and error conditions (400 if not found or not belonging to user). Without annotations, it provides good behavioral context beyond the schema.

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 front-loaded with the main action and efficiently lists return fields and error conditions. While the list of fields is detailed, it is still concise and each sentence adds value.

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?

In the absence of an output schema, the description thoroughly explains what is returned and the error scenario. It is complete enough for a simple get operation, though it could mention prerequisites like authentication.

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 description coverage is 0%, and the description does not explicitly describe the 'profile_id' parameter. It only mentions 'by id' in the purpose, adding minimal additional meaning. The parameter is simple, but the description could have provided more clarity.

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 'Get the full configuration of a single traffic profile by id', using a specific verb and resource. It distinguishes from sibling tools like tm_list_profiles (which lists all profiles) and tm_update_profile.

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 implies usage when you have a profile ID, but it does not explicitly state when to use this tool versus alternatives such as tm_list_profiles or tm_update_profile. No guidance on when not to use it.

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