odata_query

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

No annotations provided, so description carries full burden. Reveals it's OData 3.0 and supports standard query options. However, missing details like authentication requirements, rate limits, or response structure. Describes behavior minimally.

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, front-loaded with purpose, second sentence listing capabilities. No unnecessary words, efficient and to the point.

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?

With 8 parameters and no output schema, the description does not explain the return format (likely an OData JSON envelope). However, for a technical audience familiar with OData, the description covers core usage. Could mention that output is a JSON array of entities, but not a major gap.

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 coverage is 100% with descriptions for all parameters. The description adds context that the tool supports OData and lists operators, but this largely restates schema. No additional semantics like valid patterns or formatting hints beyond examples in 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 states it performs arbitrary OData 3.0 queries to any 1C entity, listing supported query options. This distinguishes it from sibling tools like get_documents or list_entities which are likely simpler or specific entity queries.

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?

No explicit when-to-use or when-not-to-use guidance. The description implies flexibility by listing supported OData features, but does not contrast with sibling tools like get_catalogs or get_documents that may be simpler, nor mention alternatives.

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