avito_get_section

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

Annotations declare readOnlyHint=true, which matches the read-only nature. The description adds the return structure (list of operation_id, method, path, safety, summary) and the source of the section name, providing useful context beyond the annotations. It does not mention error behavior, but for a simple read operation this is acceptable.

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 compact and well-structured with Args and Returns sections. The main purpose is front-loaded, and every sentence adds value without redundancy.

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?

The tool has a single parameter, an output schema is present (though not shown), and the description covers purpose, parameter source, and return format. It lacks explicit mention of error handling or limits, but for a straightforward list endpoint this is likely 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 schema has no description for the 'section' parameter (0% coverage), but the description fully compensates by explaining it's a section name, directing to avito_list_sections for valid values, and giving an example ('statistics'). This makes the parameter's meaning clear and actionable.

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 tool lists all endpoints in a given section, with a specific verb and resource. It references avito_list_sections for obtaining section names, which distinguishes it from sibling tools that list sections or search methods.

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?

It provides a pointer to avito_list_sections for the section parameter, implying you need to list sections first. However, it does not explicitly state when to use this tool over alternatives like avito_search_methods or avito_map, leaving the decision to the agent.

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