Postify

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

Annotations already declare destructiveHint=true, openWorldHint=true, non-idempotent, non-read-only, so the risk profile is largely covered. The description adds one genuinely useful behavioral fact beyond annotations — that execution happens in an 'isolated sandbox' — but says nothing about timeout limits, available APIs, network/destructive side effects of the orchestrated calls, or resource constraints.

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?

Two tight sentences with the core action and environment front-loaded; nothing is wasted. The second sentence is a pointer out of the definition rather than content, which slightly weakens it.

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?

An output schema exists and the annotations carry the safety profile, so return values and risk need not be re-explained. Still, for arbitrary code execution the description leaves the actual contract (what APIs exist, limits, failure behavior) entirely to external server instructions, which is thin for a tool of this complexity.

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?

Only one parameter exists and schema_description_coverage is 100%, so the schema already explains that it is a TypeScript program body that must `return` its result and may call external_* functions. The description adds no syntax, length, or format detail beyond that, so the baseline 3 applies.

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?

Specific verb (run) plus resource (a short TypeScript program) plus scope and environment (isolated sandbox, orchestrating Postify MCP tools). It also names the sibling search_tools as the way to locate the tools being orchestrated, so the agent can separate this from search_tools itself.

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 implies the use case (orchestrate MCP tools in code) and points to search_tools for discovering callable tools, which is real routing guidance. However, it gives no explicit when-not conditions, no alternative to writing code, and defers the operative contract to 'server instructions' rather than stating it.

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

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so safety is covered. The description usefully adds the return format (TypeScript declarations) and the connection-scoped result set, but says nothing about result size, truncation, or pagination.

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?

Two tight sentences with the core purpose front-loaded. The pointer to server instructions is a slight deferral, but it costs little and signals where deeper contract detail lives.

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?

An output schema exists so return values needn't be described, and the single optional param is fully specified. However, for a discovery tool the description leans on external 'server instructions' an agent may not have in context, leaving the full contract unresolved.

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 coverage is 100% and the query parameter is fully documented (case-insensitive substring over name/title/description, omit for all). The description adds nothing about the parameter, so the baseline 3 applies.

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?

States a specific verb ('Find') and a scoped resource ('Postify MCP tools this connection can reach'), plus the return form (TypeScript declarations). It distinguishes itself from the sibling by naming execute_typescript as the consumer, though it doesn't explicitly frame it as an alternative.

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 implies the workflow (search first, then call results from execute_typescript) but never states when to search versus when to call execute_typescript directly. 'See the server instructions for the full contract' offloads guidance rather than providing it.

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