List Installed Blocks

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

No annotations provided, description implies a read operation without side effects, but does not explicitly state safety or constraints. Adequate but not detailed.

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 short sentences covering function, purpose, and optional filter. No redundant information.

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?

Lacks details on output format or pagination, but given it's a list tool with no output schema, description is sufficient for basic use. Could be improved with return structure.

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 covers the only parameter fully; description adds 'optionally filter' which is already in schema. Minimal added value beyond schema.

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 it lists installed blocks in the project, with ability to filter by name. Distinguishes from siblings like listBlocks (all blocks) and getBlockInstall (single install).

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?

Mentions use case for customization/updating but lacks explicit exclusion or comparison with sibling tools. Agent might need to infer when not to use.

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