get_methodology

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the endpoint is free and requires no API key, which is key operational behavior. The 'Get' verb implies read-only, and the description explains what content will be returned (methodology details). While it does not mention rate limits or response format, the provided traits are sufficient for this simple endpoint.

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 two sentences, front-loaded with the primary action ('Get the SignalScope platform methodology') and followed by a brief elaboration on content and access requirements. Every word adds value, with no fluff or redundancy. It is appropriately sized for a simple no-parameter tool.

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 zero-parameter tool with no output schema, the description fully covers what the tool does, what it returns, and any access constraints. The mention of 'free endpoint — no API key required' covers operational context, and the elaboration on signal handling completes the functional picture. No gaps are apparent given the tool's simplicity.

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 has zero parameters, and the schema coverage is 100% (empty schema). Per calibration guidelines, '0 params = baseline 4'. The description does not need to add parameter details, and no additional semantic explanation is required beyond what the schema already conveys.

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 the SignalScope platform methodology' with a specific verb and resource. It elaborates on what the methodology covers (harvested, scored, filtered, staged) and distinguishes it from sibling tools like get_signals or get_platform_stats, which serve different purposes.

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 clear usage context by noting 'Free endpoint — no API key required,' which tells the agent when this tool can be used without authentication. It does not explicitly name alternatives or exclusions, but given the unique subject matter, this is not necessary. The guidance is clear for a low-risk informational endpoint.

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