get_executive_trading

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

No annotations are provided, so the description carries full burden. It mentions 'analysis' which implies processing/interpretation beyond raw data retrieval, but doesn't disclose behavioral traits like whether this is a read-only operation, what format the analysis takes, whether it involves external data sources, or any rate limits/authentication requirements. The description is insufficient for a tool with analytical claims.

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 a single, efficient sentence that front-loads the core purpose. There's no wasted verbiage, though it could benefit from structural separation of purpose from additional context. Every word contributes to understanding the tool's analytical focus.

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?

For a tool claiming 'analysis' with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the analysis entails, what format results take, or how parameters affect the analysis. The agent lacks crucial information about behavioral expectations and output structure.

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 description coverage is only 33% (only 'corp_code' has a description). The description adds no parameter-specific information beyond what's implied by the tool's purpose. It doesn't explain what 'start_date' and 'end_date' filter, the expected date format, or what happens when they're null. With low schema coverage, the description fails to compensate adequately.

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: analyzing insider trading suspicions and management signals through executive and major shareholder stock trading. It specifies the resource (executive/major shareholder trading) and the analytical goal, though it doesn't explicitly differentiate from sibling tools like 'get_major_holder_changes' or 'get_major_shareholder_changes' which might cover similar data.

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 prerequisites, timing considerations, or how it differs from sibling tools that might retrieve related information about major shareholders or executive compensation. The agent must infer usage from the purpose alone.

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