Set agency profile

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that it 'creates or replaces', which aligns with destructive. However, it does not disclose additional behavioral traits such as irreversible changes, required permissions, or performance impact.

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 wasted words, achieving conciseness. However, it lacks structure such as bullet points or sections; a slightly more structured format could improve scannability without adding length.

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 tool has 7 parameters (including complex nested services), no parameter descriptions, and a minimal description, the contextual completeness is low. The agent lacks guidance on what each field means or how to use the tool effectively.

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 schema description coverage is 0%, meaning no parameter descriptions exist in the schema. The description provides no explanation of parameters (name, services, notes, targetMarkets, etc.). The agent receives no semantic guidance beyond the schema's type constraints.

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 the verb 'creates or replaces' and the resource 'local agency profile', with a specific purpose 'used for fit and doability scoring'. This distinguishes it from sibling tools like agency_profile_get (retrieval) and opportunity_* tools.

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 implies usage for setting the agency profile but does not explicitly state when to use this tool versus alternatives (e.g., agency_profile_get) or when not to use it. No usage context, prerequisites, or side effects are mentioned.

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