tmgmt_capabilities

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: no API key is required, and everything listed is a public no-auth route. It does not clarify return shape, rate limits, or whether the list can change, so behavioral coverage is adequate but incomplete.

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?

Front-loaded with the core value proposition and padded only with two short supporting fragments ('No API key needed', 'Start here if you are unsure'). Every clause is relevant, though the sentence is slightly fragmented rather than perfectly tight.

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?

With no parameters, no annotations, and no output schema, the description supplies enough to call it: what it returns (public no-auth routes with their parameters) and the auth precondition. The absence of any note on response format is minor for a zero-argument discovery endpoint.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies it is called with no arguments and needs no auth, and there are no parameters whose meaning could be left ambiguous.

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?

Names a specific resource and output: 'the machine-readable list of every public no-auth route with its parameters.' This is clearly a discovery/capabilities tool and is distinguishable from functional siblings like domains_get_quote or orders_dry_run. It stops short of explicitly naming a sibling it complements, which would push it to a 5.

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?

'Start here if you are unsure' gives a concrete condition for reaching for this tool before others. However, it never states when NOT to use it or names an alternative path once you are no longer unsure, so the routing guidance is contextual rather than explicit.

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