submit_feed

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

The description mentions raising BingWebmasterError on failure, which adds transparency beyond the schema. However, with no annotations, it lacks disclosure of side effects, permissions, or other behavioral traits.

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 extremely concise with an efficient front-loaded purpose statement, followed by clear Args and Raises sections. Every sentence adds value.

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?

Given the presence of an output schema and sibling tools, the description covers purpose, parameters, and error behavior adequately but misses usage context and the 'self' parameter. An agent could invoke the tool but might lack full understanding.

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 description explains site_url and feed_url with brief definitions, adding value beyond the schema's titles and types. However, the required 'self' parameter is not explained, and schema coverage is 0%, so the description only partially compensates.

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 'Submit a sitemap feed for indexing' with a specific verb and resource, distinguishing it from sibling tools like 'get_feeds' and 'remove_feed'.

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 description provides no guidance on when to use this tool versus alternatives like 'submit_url' or 'submit_content', nor does it mention prerequisites or exclusions.

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