get_sieve_script

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

No annotations are provided, so the description must cover behavioral aspects. It discloses that the content is downloaded from blob storage, which is a useful behavioral detail. However, it does not mention any side effects (none expected), required permissions, or rate limits. The description adds some value beyond the function name but is not fully comprehensive.

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, well-structured sentence that efficiently conveys the purpose and a key detail. No extraneous words; every word adds value.

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?

Given the low complexity (single parameter) and presence of an output schema, the description is fairly complete. It explains the action, resource, and a technical detail (blob storage). It could mention error scenarios or validation of script_id, but for a simple getter, it is sufficient.

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 single parameter 'script_id' has a 0% schema description coverage. The tool description merely says 'by ID', which repeats the parameter name without adding semantic details such as the expected format, example, or source. For a parameter with no schema description, the description should compensate more, but it does not.

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 explicitly states the verb 'Get', the resource 'Sieve script', and adds specificity with 'by ID, including its full content (downloaded from blob storage)'. This clearly distinguishes it from sibling tools like list_sieve_scripts (which lists all scripts) and create_sieve_script (which creates a new one).

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 tool is used when a specific Sieve script is needed, but it does not provide explicit guidance on when to use it vs. alternatives like list_sieve_scripts or when not to use it. No prerequisites or contexts are mentioned.

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