check_construction_permit

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

No annotations provided; description outlines returned fields (stages, dates, history) but does not disclose access requirements, side effects, or rate limits. 'Pro tariff' hints at restrictions but is vague.

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?

Single sentence conveys purpose and key outputs efficiently, though Russian acronyms may require domain knowledge.

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?

For a simple read tool with output schema, description covers main functionality; jargon ('РНС') slightly reduces completeness but is acceptable for the domain.

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 already describes the single parameter (object_id) with 100% coverage; description adds no extra parameter meaning 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?

Description clearly specifies the tool retrieves construction permit details (stages, dates, history) for an object, distinguishing it from siblings like check_developer or get_project_declaration.

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?

Implied usage for permit info, but no explicit when-to-use, when-not, or alternatives mentioned despite sibling tools available.

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