ths_get_score_tokens_post

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

Lacks annotations; description only notes HTTP method. No disclosure of side effects, permissions, rate limits, or idempotency, leaving behavioral assumptions unclear.

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?

Single sentence is highly concise and front-loaded. However, brevity sacrifices completeness; it could benefit from a structured breakdown.

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?

Despite moderate parameter count and no output schema, the description omits return format, error handling, and parameter details, making it incomplete for an agent.

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?

Only 'tokenMints' is hinted via 'selected token mints'. Parameters 'wallet', 'debug', and 'breakdown' are unexplained, and schema has no descriptions, so the description adds minimal meaning.

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 the tool fetches THS scores for selected token mints using POST, distinguishing it from the GET variant. However, it does not explain what 'THS score' represents, which may require domain knowledge.

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 POST vs GET or other sibling tools like ths_get_score. The description offers no context for selection.

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