add_documentation_to_knowledge_base

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description's only added behavioral fact is that the tool is deprecated upstream, which is genuinely useful context not present in the annotations, but it reveals nothing about mutation effects, permissions, or failure modes.

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?

Extremely short and front-loaded, but it is a sentence fragment rather than a complete, appropriately sized description. It avoids waste but errs toward under-specification for a 6-parameter tool.

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 6-parameter mutation tool with no output schema, the description omits what gets added, how the url vs file_path vs file_base64 inputs differ in use, and what a caller should do instead given the deprecation. The deprecation warning is the sole piece of usable context.

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 83%, so the schema already documents url, name, file_path, file_base64, and file_filename. The description adds no parameter meaning whatsoever (agent_id is undocumented in both places), so the baseline 3 applies with no uplift.

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 text "Add To Knowledge Base" essentially restates the tool name without adding a specific verb+resource elaboration or differentiating it from siblings like add_from_file or create_file_document_route. The only extra information is the deprecation status, which is a status token rather than a purpose statement, so this reads as near-tautology.

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?

"Deprecated upstream" implies the agent should prefer alternatives, which is weakly useful guidance, but the description names no replacement tool and states no conditions for when (if ever) this should still be invoked. No when-to-use, when-not-to-use, or alternative is explicit.

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