segnals_get_bot_logs

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

Discloses content including cold-start status and recent activity. Mentions required scope but does not describe read-only nature, rate limits, default time range, ordering, or pagination. With no annotations, additional behavioral details would strengthen this score.

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 plus a code example: first states purpose, second describes content, third explains when to use and required scope. Example clarifies invocation. No redundant information.

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?

Describes output content (activity, errors, system events, cold-start status) and supports debugging use case. Lacks output schema but provides sufficient context for a logs tool. Could mention ordering (e.g., descending by time) or pagination.

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 has 100% coverage with clear descriptions for bot_id (integer, exclusiveMinimum>0) and limit (min 1, max 200, default 50). Description adds no new parameter info beyond the schema, so baseline 3 is appropriate.

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?

Explicitly states 'Get execution logs for a specific bot' and details content: trading activity, errors, system events including cold-start status. Clearly distinguishes from sibling tools like segnals_get_bot (configuration) and segnals_get_trades (trade list).

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?

Provides direct guidance: 'Use this to debug bot behavior or check recent activity.' Also specifies required scope 'read:bots'. Does not explicitly state when not to use, but context implies debugging and recent activity checking.

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