sally_explain

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

Beyond readOnlyHint, adds no-storage/no-training privacy guarantee, markdown output format, and premium tier info. Does not detail any potential dynamic behavior but adds significant context.

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?

Description is moderately long (5 sentences) but every sentence serves a purpose: purpose, usage, privacy, read-only, output, premium. Front-loaded with core action.

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 all essential aspects for agent invocation: purpose, when to use, privacy, read-only nature, return format, and usage limits. No output schema but return format is described.

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%, so baseline is 3. Description adds minimal extra meaning: only mentions that 'content' is the code and 'lang' is optional. Sufficient but not enhanced.

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 the verb 'explain' and resource 'code', with a distinctive tone ('plain English, no hand-holding'). Differentiates from siblings by focusing on code explanation rather than brainstorming or refactoring.

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?

Explicitly describes when to use: 'when the user wants a snippet or file explained, asks what does this do, or inherited code nobody documented.' Provides clear context and implicit alternative avoidance.

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