screen_candidate

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

Adds context beyond annotations (offline, propose-only, fetching price history on demand). Aligns with readOnlyHint and openWorldHint. No contradictions.

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, each informative. Front-loaded purpose, followed by behavioral notes and constraints. No wasted words.

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?

Covers input, process, constraints (offline, propose-only), output characteristics (reasons with figures), and edge case (price history fetch). Output schema exists, so no need to detail return values.

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 0% coverage, but description clarifies that 'ticker' is a NEW candidate to judge. Single parameter and purpose-driven description compensate for lack of schema detail.

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?

Clearly states verb 'Judge' and resource 'a NEW ticker against the user's book', with explicit use case 'is TICKER a good fit'. Distinct from siblings which focus on portfolio-level analysis.

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 explicit use case and what the tool is not for (buy recommendation, return forecast). Mentions conditional behavior with ASSET_MCP_OFFLINE, but does not list alternative tools for other scenarios.

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