get_symbols

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it says nothing about permissions, session requirements, filtering behavior, or result limits. Only the word "Get" hints at a read-style retrieval, which is weak disclosure for a zero-annotation 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?

It is short and front-loaded, but this is under-specification rather than conciseness — a single fragment with no useful detail, and the "(is)" token is opaque to an unknown reader.

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?

An output schema exists, so return values need not be explained. But three undocumented parameters, no annotations, and no usage context leave the definition materially incomplete for an agent trying to invoke it correctly.

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 description coverage is 0%, and the description mentions no parameters at all. The three parameters (session_id, exports_only, imports_only) are entirely undocumented, and the parenthetical "(is)" gives no meaningful hint about the export/import filtering.

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?

It gives a verb ("Get") and a resource ("binary symbols"), so the basic action is identifiable. However, it does not distinguish itself from nearby siblings like get_imports, get_strings, or list_functions, and the cryptic parenthetical "(is)" adds no clarity about scope or content.

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?

There is no statement of when to use this tool versus alternatives such as get_imports, get_strings, or list_functions. Only the name implies it is a symbol-listing read, leaving the agent to guess at appropriate context.

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