get_config

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds no behavioral context beyond 'Get', such as not-found behavior, response format, or side effects, so it contributes nothing beyond what annotations already provide.

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 a single sentence with no filler, stating the operation and the key qualifying detail. It is front-loaded and easy to parse.

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 one-parameter read-only getter with strong annotations, the description is largely sufficient. It does not mention error behavior when the ID does not exist or the exact return shape, but 'Get a saved scrape configuration by ID' adequately conveys the expected result for a simple retrieval tool.

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?

There is a single required config_id parameter with 0% schema description coverage, so the description must compensate. The phrase 'by ID' explicitly ties the parameter to the saved scrape configuration, which is helpful, but it adds no format, source, or validation detail beyond what the parameter name config_id already implies.

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 states a specific verb (Get), a clear resource (saved scrape configuration), and the selection criterion (by ID). This distinguishes it from list_configs, which lists multiple configurations, and from create_config, update_config, and delete_config.

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 phrase 'by ID' implies the tool should be used when a specific config_id is known, but there is no explicit guidance about when to use this tool versus alternatives. It does not mention that list_configs can be used to discover configuration IDs or that update_config is for modifications, so usage guidance is only implicit.

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