get_legislation_block

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the tool retrieves a block, implying a read operation, but does not mention any potential side effects, permissions, rate limits, or output format. This is minimal but adequate for a simple retrieval tool.

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 sentences, no redundant words. The description is front-loaded with the core purpose and immediately provides usage guidance. Every sentence 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 simple tool (2 required params, no output schema, no annotations), the description is mostly complete. It explains what the tool does and how to use it. However, it could mention what the output looks like (e.g., returns block content) since there is no output schema.

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 input schema has 100% coverage with clear parameter descriptions. The description adds context by specifying block types (article, disposition, annex), which enhances understanding beyond the schema alone. However, the schema already does a good job, so the added value is moderate.

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 clearly states the verb 'Get' and the resource 'specific block (article, disposition, annex) from a law'. It also references the sibling tool get_legislation_structure, which helps distinguish it, but fails to explicitly differentiate from other sibling tools like get_legislation_details or get_legislation_text.

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 provides clear guidance to use get_legislation_structure first to discover block IDs. However, it does not mention when not to use the tool or suggest alternative tools besides the one referenced.

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