fetch_profit

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the tool returns 'Stringified JSON response with profit summary, or None if failed,' which gives some insight into output behavior. However, it lacks critical details such as whether this is a read-only operation, what data sources it queries, potential rate limits, or error conditions beyond failure. For a tool with zero annotation coverage, this is insufficient.

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 appropriately sized and front-loaded, with the core purpose stated first followed by parameter and return details. It uses clear sections ('Parameters:', 'Returns:') for structure. However, the mention of 'ctx' as a parameter could be confusing since it's not in the schema, slightly reducing efficiency.

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 the tool's moderate complexity (financial data retrieval), no annotations, no output schema, and 0 parameters, the description is minimally adequate. It explains the purpose and return behavior but lacks details on data format, error handling, or how it differs from siblings. It meets basic needs but has clear gaps for effective agent use.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description mentions 'ctx (Context): MCP context object for logging and client access,' which adds context about an implicit parameter not in the schema, providing useful semantic information. This compensates well for the schema's completeness.

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 the tool's purpose: 'Get profit summary for the trading bot.' This is a specific verb ('Get') + resource ('profit summary') combination that tells what the tool does. However, it doesn't explicitly distinguish this from similar sibling tools like 'fetch_performance' or 'fetch_balance,' which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when it's appropriate to fetch profit summary versus other financial metrics like balance or performance, nor does it specify any prerequisites or conditions for use. This leaves the agent without contextual usage instructions.

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