tm_list_profiles

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

Discloses return format (id, name, createdAt), ordering behavior (server-default, no sort), and ownership scope. No annotations provided, but description adequately covers behavior for a read-only list tool.

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?

Three sentences, front-loaded with purpose, no superfluous text. Every sentence adds critical information (purpose, return format, sibling reference, ordering constraint).

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 zero parameters and the presence of an output schema, the description fully covers what the agent needs: purpose, output structure, ordering, and guidance for more detail. No gaps.

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?

No parameters exist; schema coverage is 100%. Description adds value by explaining return structure and ordering, meeting the baseline expectation for zero-parameter tools.

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?

Description clearly states 'List all traffic profiles owned by the authenticated user', specifying verb, resource, and scope. Distinguishes from sibling tm_get_profile by noting it returns lightweight summaries vs full config.

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?

Explicitly directs to tm_get_profile for full details, implying when to use this tool for summaries. Does not state when not to use but provides clear context and a practical alternative.

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