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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnly=false, so the safety profile is covered. The description contributes the auth requirement ("Requires API key"), which annotations do not express, but says nothing about what gets overwritten, whether an existing profile is replaced, or what Smithery rejects.

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?

Three short sentences with the hard prerequisite (API key) front-loaded and no filler. The middle sentence is somewhat awkwardly compressed, but nothing is wasted.

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 26-parameter destructive write with a nested object, no output schema, and near-zero schema documentation, the description is far too thin. Key field-level and side-effect information an agent needs to call this correctly is absent.

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?

With 26 parameters at only 8% schema description coverage, the description must carry most parameter semantics and does not. It only alludes to endpoint_url/smithery_name constraints and says nothing about transport, auth_type, remote_access, runtime_environment, or directory_categories.

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?

"Save accurate public profile fields" implies writing a server profile record, but the description never says it creates a new MCP server entry, nor how it relates to list_servers or check_launch_coverage. The title "Save MCP profile" restates the same vagueness rather than clarifying the verb+resource.

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?

"before checking all selected destination prerequisites" gives a useful ordering hint relative to the coverage/preflight siblings, but no explicit when-to-use/when-not-to-use and no naming of alternatives. An agent must infer the ordering from a subordinate clause.

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